If I remember correctly, I was going through a tutorial on the autotools and it made reference to needing the file and didn't say what went into it.<br><br>I ended up at the autotools via the links in the Chinook pages somewhere. I would prefer to follow a standard layout/environment and after looking at a couple examples and not really seeing one, this is where I ended up.
<br><br>I'm new to the Linux programming environment and at work I've always had to setup the build environment myself.<br><br>Thanks for you time.<br><br>Bill<br><br><div class="gmail_quote">On Dec 17, 2007 3:07 AM, Eero Tamminen <
<a href="mailto:eero.tamminen@nokia.com">eero.tamminen@nokia.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
Hi,<br><br>ext William Hope wrote:<br></div><div class="Ih2E3d">> Thanks for replying. No, no .o is produced. Based on your emal, I tired to<br>> narrow it down.<br>><br>> This doesn't work:<br>><br>> [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk/src] > source='
pPimString.cpp'<br>> object='pPimString.o' libtool=no depfile='.deps/pPimString.Po'<br>> tmpdepfile='.deps/pPimString.TPo' depmode=none /bin/sh ../config/depcomp g++<br>> -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o
pPimString.o pPimString.cpp<br>><br>> This does:<br>><br>> [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk/src] > source='pPimString.cpp'<br>> object='pPimString.o' libtool=no depfile='.deps/pPimString.Po'
<br>> tmpdepfile='.deps/pPimString.TPo' depmode=none g++ -DHAVE_CONFIG_H -I. -I.<br>> -I.. -g -O2 -c -o pPimString.o pPimString.cpp<br>><br>> So the /bin/sh ../config/depcomp part is what's screwing me up. I looked at
<br>> the depcomp scripts that came with the hello-world-app-0.5.1 & maemopad-2.1.<br>> These were identical, so I copied it and I seem to be in business.<br><br></div>I'm not that familiar with autotools (I use just make & pkg-config
<br>myself). Where did you got the depcomp you were using earlier?<br><font color="#888888"><br><br> - Eero<br></font><br>PS. Please put CC on the devel list, other developers might have<br>a similar problem (and I haven't seen this mentioned earlier on
<br>the list), so it helps if they can find the answer with Google. :-)<br><div><div></div><div class="Wj3C7c"><br><br>> Thank you very much!<br>><br>> Bill<br>><br>><br>> On Dec 14, 2007 6:25 AM, Eero Tamminen <
<a href="mailto:eero.tamminen@nokia.com">eero.tamminen@nokia.com</a>> wrote:<br>><br>>> Hi,<br>>><br>>> ext William Hope wrote:<br>>>> I'm having a problem getting the build tools properly configured. I've
<br>>> read<br>>>> various online articles/books/docs and I have a start. The problem is<br>>> that<br>>>> it doesn't compile anything. Below is output & directory structure. I<br>>> can't
<br>>>> really concentrate on developing until I can simplify builds.<br>>>> I know it's not invoking the compiler as some of the files have errors.<br>>> If I<br>>>> compile by hand, then it doesn't 'attempt' to compile them.
<br>>>><br>>>> Can anyone help? Point me to a better place to ask?<br>>> So calls like this don't produce .o files:<br>>>> source='sio.cpp' object='sio.o' libtool=no \<br>
>>> depfile='.deps/sio.Po' tmpdepfile='.deps/sio.TPo' \<br>>>> depmode=none /bin/sh ../config/depcomp \<br>>>> g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp<br>>> What if you call it with -v from the command line:
<br>>> g++ -v -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp<br>>><br>>><br>>> - Eero<br>>><br>><br><br></div></div></blockquote></div><br>