Author Topic: dev environment step by step  (Read 3594 times)

Anonymous

  • Guest
dev environment step by step
« on: December 26, 2003, 12:38:57 pm »
Hi all,
Could you post step-by-step how to setup a native development environment for the x11 rom via NFS? I read It\'s the one over which sash works.

I tried the cross compiler from cacko but it fails (it builds x86 binaries even after running the \"sh\" script). After all, I think a NFS one is the best because it doesn\'t take space.

I am willing to build some apps and contribute them to the feed:
  - freecraft
  - evolution (I will try with 1.2.4 first)
  - A freehand notes taking app

Fernando Monera
http://www.opensistemas.com

Anonymous

  • Guest
dev environment step by step
« Reply #1 on: December 26, 2003, 09:34:20 pm »
Try

Code: [Select]
export CC=arm-linux-gcc

after running the script. Or better yet, put it in the script. There might be more things that need to be set, but that should be enough to get you going.

Also, if the thing you are trying to compile is using a configure script that calls gtk-config or sdl-config, take a look at those scripts and change them to make them have the right paths. i.e. you don\'t want any references to /usr/lib or other locations of native x86 libraries or you get errors trying to link.

sashz

  • Sr. Member
  • ****
  • Posts: 388
    • View Profile
    • http://
dev environment step by step
« Reply #2 on: December 27, 2003, 01:45:43 am »
unpack cross tools from root ( \"/\" ) directory (you need be as root),
tools will extcraxting in /usr/local/arm/3.3.1/

for setup vars and paths run (from user account):
/usr/local/arm/3.3.1/runzgcc.sh

for program compilation use CC=arm-linux-gcc CXX=arm-linux-g++
for configuring sources use --host and --build:
./configure --host=arm-linux --build=i686-linux

if sources need x11 libraries/headers:
./configure --host=arm-linux --build=i686-linux --x-includes=$X11INC --x-libraries=$X11LIB

for GTK and QT variables:
home dir - $GTKDIR and $QTDIR
for includes - $GTKINC
for libraries - $GTKLIB

Anonymous

  • Guest
dev environment step by step
« Reply #3 on: December 27, 2003, 03:41:00 am »
Ok thanks.
I\'ll post the results.

Fernando Monera
http://www.opensistemas.com

Anonymous

  • Guest
dev environment step by step
« Reply #4 on: December 30, 2003, 09:36:19 pm »
WOW!!!! I have a working dev environment using the native compiler with NFS mount and using distcc. It works very good. I have many programs and libs working!!!

Now I need to know how to use \"checkinstall\" to start making ipks. This is what I do:

1) ./configure ....
2) make
3) checkinstall

After answering some questions (and watching the \"make install\" output) it creates an ipk in /var/tmp which is almost empty. It seems that checkinstall isn\'t detecting the changes. With debug option turned on, I see that the \"package\" dir is not holding many files.

I installed installwatch from sources which is missing from the checkinstall ipk.

Any hints?

Fernando Monera
http://www.opensistemas.com

Anonymous

  • Guest
dev environment step by step
« Reply #5 on: January 01, 2004, 11:18:27 pm »
I\'ve installed the native development tools but when I do a configure on a project (I\'m building cgoban - a go game) I get:

checking for sys/in.h... cat: write error: No space left on device

The \'no space left\' occurs at different points. Any ideas what I should look at? My df-h looks like:

Filesystem                Size      Used Available Use% Mounted on
/dev/root                25.0M     25.0M         0 100% /
/dev/ram1                44.0k     26.0k     18.0k  59% /dev
/dev/cloop               41.6M     38.8M    683.0k  98% /usr
/dev/mtdblock3           96.0M     24.5M     71.5M  25% /home
none                     10.0M      1.6M      8.4M  16% /dev/shm
/dev/mmcda1             475.9M    181.1M    270.2M  40% /home/system/var/mnt/car          d
/dev/loop0               39.2M     39.2M         0 100% /home/root/usr/local/arm

I also notice the native development tools don\'t include the X11 headers and libraries, etc. Am I doing something wrong?

Chris.

Anonymous

  • Guest
dev environment step by step
« Reply #6 on: January 01, 2004, 11:51:59 pm »
Oops, false alarm. The no space on device seems to be caused because the Zaurus thinks the SD card is full even though it reports only half the space used. Deleting some files enabled the configure to continue.

For native compilation though I\'m still interested in finding out how to get the X11 libraries and include files on the Zaurus.

Chris.