[maemo-developers] Having problems getting build enviroment set up (Chinook)

[From: Eero Tamminen]

Hi,

ext William Hope wrote:
> Thanks for replying. No, no .o is produced. Based on your emal, I tired to
> narrow it down.
> 
> This doesn't work:
> 
> [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk/src] > source='pPimString.cpp'
> object='pPimString.o' libtool=no depfile='.deps/pPimString.Po'
> tmpdepfile='.deps/pPimString.TPo' depmode=none /bin/sh ../config/depcomp g++
> -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o pPimString.o pPimString.cpp
> 
> This does:
> 
> [sbox-SDK_BETA_X86: ~/prgms/ppim/trunk/src] > source='pPimString.cpp'
> object='pPimString.o' libtool=no depfile='.deps/pPimString.Po'
> tmpdepfile='.deps/pPimString.TPo' depmode=none  g++ -DHAVE_CONFIG_H -I. -I.
> -I.. -g -O2 -c -o pPimString.o pPimString.cpp
> 
> So the /bin/sh ../config/depcomp part is what's screwing me up. I looked at
> the depcomp scripts that came with the hello-world-app-0.5.1 & maemopad-2.1.
> These were identical, so I copied it and I seem to be in business.

I'm not that familiar with autotools (I use just make & pkg-config
myself). Where did you got the depcomp you were using earlier?


	- Eero

PS. Please put CC on the devel list, other developers might have
a similar problem (and I haven't seen this mentioned earlier on
the list), so it helps if they can find the answer with Google. :-)


> Thank you very much!
> 
> Bill
> 
> 
> On Dec 14, 2007 6:25 AM, Eero Tamminen <eero.tamminen at nokia.com> wrote:
> 
>> Hi,
>>
>> ext William Hope wrote:
>>>  I'm having a problem getting the build tools properly configured. I've
>> read
>>> various online articles/books/docs and I have a start. The problem is
>> that
>>> it doesn't compile anything. Below is output & directory structure. I
>> can't
>>> really concentrate on developing until I can simplify builds.
>>> I know it's not invoking the compiler as some of the files have errors.
>> If I
>>> compile by hand, then it doesn't 'attempt' to compile them.
>>>
>>> Can anyone help? Point me to a better place to ask?
>> So calls like this don't produce .o files:
>>> source='sio.cpp' object='sio.o' libtool=no \
>>> depfile='.deps/sio.Po' tmpdepfile='.deps/sio.TPo' \
>>> depmode=none /bin/sh ../config/depcomp \
>>> g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp
>> What if you call it with -v from the command line:
>>   g++ -v -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o sio.o sio.cpp
>>
>>
>>        - Eero
>>
>