[OGo-Developer] noob question on building sope-appserver/samples/HelloForm

Chad Leigh developer@opengroupware.org
Sun, 29 Oct 2006 21:43:40 -0700


On Oct 29, 2006, at 3:23 AM, Helge Hess wrote:

> On Oct 29, 2006, at 07:46, Chad Leigh wrote:
>> gcc        -o HelloForm.woa/./HelloForm ./shared_debug_obj/ 
>> HelloForm.o ./shared_debug_obj/Main.o \
>>           -L/Volumes/erik/Users/chad/GNUstep/Library/Libraries/   - 
>> L/usr/local/lib -L/usr/lib   -lNGObjWeb -lNGMime -lNGStreams - 
>> lNGExtensions         -lNGMime -lNGStreams -lNGExtensions - 
>> lEOControl -lXmlRpc -lDOM -lSaxObjC -lEOControl -lDOM -lXmlRpc - 
>> lSaxObjC   -framework Foundation       -lm
>> /usr/bin/ld: can't locate file for: -lNGObjWeb
>> collect2: ld returned 1 exit status
>
> Debug/non-debug builds are somehow mixed up. The GCC above is  
> looking for "-lNGObjWeb" while it should look for "-lNGObjWeb_d".
> This name rewriting is done by a small tool called  
> "which_lib" (contained in the GNUstep tree).
>
> But apparently you did you say "make debug=yes" (shared_debug_obj),  
> so I think it should work.

Ok, I did not explicitly do any make debug=yes.  I just did make when  
beuilding the sope-appserver stuff and the samples.

I will go and do an explicit make debug=yes everywhere.

Actually, in reviewing the web instructions, it has a ./configure -- 
enable-debug showing for building SOPE so I guess I do have it built  
that way.

If I do, in the sample HelloWorld or HelloForm, make debug=yes, I  
still get the error.

> Did you use the gstep-make which comes with SOPE 4.5?

Yes, I did make and make install the gstep-make that comes with SOPE  
4.5.

Does that  make a new version of make or just set up the environment  
in the GNUStep directory?  The latter is what it appears to do from  
the make install output messages.

>
> (Notably this special debug renaming is removed in the very latest  
> gnustep-make because users frequently mix up debug=yes/no, but I  
> didn't try that on OSX yet).
>
>
> BTW: if you install SOPE into /usr/local, you don't need to source  
> GNUstep.sh at dev or runtime.

I will look in to that. I was just following the .build it. page(s)  
from the SOPE website with the MACOSX notes.

I think this may actually help with the XCode problems as well...  I  
am NOT an XCode guru, like I said, and probably could be more  
efficient in my Cocoa programming if I were :-)

>
>
>> (It also appears from my feeble attempts that the xcode projects  
>> included for sope are for the earlier versions of xcode -- nothing  
>> even remotely builds on this system, but that is OK
>
> Works fine for me with Xcode 2.3.
>
> Hm, actually I just tried and the Xcode projects need a bit of  
> tweaking because some files got renamed/added in the PostgreSQL  
> adaptor. But besides it seems to compile fine.

Nothing compiles for me and I get over 100 errors before it gives up.  
I will mess around with it some more to see what I am doing wrong.   
Let's not worry about this at the moment.

>
>> -- I can handle the command line building [even though I have been  
>> doing Cocoa programming off and on the last many years I am also  
>> an XCode neophyte when it comes to the ins and outs of XCode -- I  
>> liked the old WO4.5 / OpenStep Project Builder :-])
>
> You should be able to trigger a GNUstep build from inside Xcode  
> using legacy targets? In fact thats what I would recommend if you  
> also want to deploy on non-Apple platforms.
>
> BTW: easiest is to use Linux, eg Debian, not Solaris or FreeBSD.  
> Comes with prebuild and tested packages.

We don't run any Linux in our shop so it is not an option.  Sorry.

best
Chad

>
> Greets,
>   Helge
> -- 
> Helge Hess
> http://docs.opengroupware.org/Members/helge/
>
>
> -- 
> OpenGroupware.org Developer
> developer@opengroupware.org
> http://mail.opengroupware.org/mailman/listinfo/developer