[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: subproject
From: |
Nicola Pero |
Subject: |
Re: subproject |
Date: |
Tue, 1 May 2007 17:26:34 +0200 (CEST) |
If -nostdlib is causing problems, I assume we can remove it from gnustep-make ?
I don't have an Apple
around to test though.
I checked and I can see that it's used on all platforms when building a
subproject. I'm not really sure why.
Also, I just checked the documentation for -nostdlib, and it mentions that
usually you want to use
-nostdlib -lgcc. So maybe instead of removing -nostdlib, we rather need to add
-lgcc ?
Thanks
PS: if you want to link directly an already compiled file, you can use:
xxx_OBJ_FILES = bindings/obj/myfile.o
-----Original Message-----
From: Yves de Champlain <yves@gnu-darwin.org>
Sent: Mon, April 30, 2007 4:55 pm
To: Yves de Champlain <yves@gnu-darwin.org>
Cc: GNUstep Discuss-gnustep <discuss-gnustep@gnu.org>
Subject: Re: subproject
Le 07-04-30 à 00:57, Yves de Champlain a écrit :
> Hi
>
> subproject have a merge command to create subproject.o
>
> on MacOSX it is
>
> OBJ_MERGE_CMD = \
> $(CC) -nostdlib -r -d ...
>
> Is -nostdlib really necessary ?
>
> That command creates an unsusable subproject.o with g++ (in
> PopplerKit)
Let me be more precise ...
The only way I can link the Popplerkit framework is to avoid bindings/
subproject.o :
rm bindings/obj/subproject.o
ADDITIONAL_LDFLAGS += bindings/obj/*.o
Is there a way to patch the GNUmakefile in order to get the same
result ?
thanks
yves
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: subproject,
Nicola Pero <=