Re: On-device development in C/C++?
 

Yes, you did not read everything I said.


So, I could not get this to work but did not need it.
If you investigate the error itself there is potential to get past it.

Re: On-device development in C/C++?
 

thats a very common error when preparing an n900 development environment of the device itself.

put your source inside the chroot image or inside /home/user.

in other words, dont try to compile from /home/user/MyDocs, because its FAT32. Or mess with ./configure to let you compile outside the source folder.

thats because with fat32 you dont get the execution bit.

clasificado

Re: On-device development in C/C++?
 

hey Nicolai,
hmm last time I tried the configure stage would fail with anything, but you are certainly more confident than myself that it should work!
this is great if so and removes one block from the way :)

it would be best of all if we could optify these build-essential packages and get dpkg-buildpackage working happily.

Re: On-device development in C/C++?
 

I must admit, I don't know if the whole configure stage work.
I am working with plain old hand written Makefiles.

Nicolai

Re: On-device development in C/C++?
 

Makefiles are elegant weapons... for a more civilized age
http://xkcd.com/297/


they work well!
I have just made libliqbase work on x86 with the ones there :)

Re: On-device development in C/C++?
 

Solved: I adapted the /etc/fstab. The home partition where I was building the software was mounted as noexec. I removed that option and it was working :)

Re: On-device development in C/C++?
 

I also prefer to compile on device, and that's my manual, how to do that with FreePascal

Re: On-device development in C/C++?
 

C Programming on Maemo Device (N 900): Mobile C programming lab :cool:
Download the following files to work with gcc
• binutils_2.18.50.20070820-4+0m5_armel.deb
• libgcc1_4.2.1-4maemo9+0m5_armel.deb
• libgomp1_4.2.1-4maemo9+0m5_armel.deb
• cpp-4.2_4.2.1-4maemo9+0m5_armel.deb
• gcc-4.2-base_4.2.1-4maemo9+0m5_armel.deb
• gcc-4.2_4.2.1-4maemo9+0m5_armel.deb
1. connect your N900 to PC and copy above files into one folder
~ $ cd ~/MyDocs //change to this folder in N900 in xterm
~/MyDocs $ cd files //here your above files are copied
~/MyDocs/files $ dpkg –i * // to run all the files in files folder
~/MyDocs/files $ vi hellowrold.c //create a c program by using vi editor
Note : for entering any letter you should press “I” to enter in to insert mode

#inlcude <stdio.h>
main()
{
Printf(“M. Reddi Prasad Reddy,IP University,Delhi”);
}

Note: to save the files click ESC and shift+: and wq! .so that your c program will be saved.
~/MyDocs/files $ gcc-4.2 hello.c // gcc compiler will compile your c program
~/MyDocs/files $ ls // you will find the output file
a.out hello.c
~/MyDocs/files $ sudo gainroot //shell root will be enabled
~home/usr/MyDocs/files # cp a.out /usr/bin // to see the output you should copy this outputfile to bin folder
~/usr/bin # chmod +x a.out // change the permissions
~/usr/bin # ./a.out
M. Reddi Prasad Reddy,IP University,Delhi


any other ideas and comments
Mail id: reddy.mrp@gmail.com

Re: On-device development in C/C++?
 

Weird spelling of the file name. Especially as you're trying to compile hello.c later on.

It's spelled "include". The function you're looking for is "printf".

ESC leaves insertion mode. The command to save and quit is "wq" by itself and one enters command mode using ":".

Use -o flag to give the generated binary a name.

Why copy the binary to /usr/bin to then run it using ./a.out ?

Re: On-device development in C/C++?
 

Corrected POST: Thank you JOORIN for your comments
~ $ cd ~/MyDocs //change to this folder in N900 in xterm
~/MyDocs $ cd files //here your above files are copied
~/MyDocs/files $ sudo gainroot //shell root will be enabled
~home/usr/MyDocs/files # dpkg –i * // to run all the files in files folder
~home/usr/MyDocs/files # vi hello.c //create a c program by using vi editor
Note : for entering any letter you should press “I” to enter in to insert mode

#include <stdio.h>
main()
{
Printf(“M. Reddi Prasad Reddy,IP University,Delhi”);
}

Note:ESC leaves insertion mode. The command to save and quit is "wq" by itself and one enters command mode using ":".
~home/usr/MyDocs/files # gcc-4.2 hello.c // gcc compiler will compile your c program
~home/usr/MyDocs/files # ls // you will find the output file
a.out hello.c

~home/usr/MyDocs/files # cp a.out /usr/bin // to see the output you should copy this outputfile to bin folder
~/usr/bin # chmod +x a.out // change the permissions
~/usr/bin # ./a.out
M. Reddi Prasad Reddy,IP University,Delhi


I have modified the post. this can help people little
i have saved the a.out to /usr/bin to execute otherwise its not able to get the permissions.:confused:
Q: but still some other N900 devices are not able to install gcc.:confused: