[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Q] PDFKit detection of GWorkspace Inspector configure at MSYS2/MING

From: Riccardo Mottola
Subject: Re: [Q] PDFKit detection of GWorkspace Inspector configure at MSYS2/MINGW32
Date: Wed, 09 Mar 2016 23:23:04 +0100
User-agent: Mozilla/5.0 (X11; FreeBSD i386; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1

Hi Seong,

Seong Gu Lee wrote:
> Googling says "You can either instruct the linker to link the
> libraries even if the symbols are not encountered using
> |-Wl,--no-as-needed| linker option as
> |gcc `gnustep-config --objc-flags` -Wl,--no-as-needed -lgnustep-base  h.m -o 
> hello|
> Or better yet just move the source to the beginning of the compilation
> command as
> |gcc h.m  `gnustep-config --objc-flags` -lgnustep-base -o hello"
> --------------------------------------|
> gcc conftest.c -o conftest.exe -xobjective-c -MMD -MP -DGNUSTEP 
> -fexceptions -fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS 
> -fno-omit-frame-pointer -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -O2 
> -fgnu-runtime -fconstant-string-class=NSConstantString -I. 
> -I/mingw32/GNUstep/Local/Library/Headers 
> -I/mingw32/GNUstep/System/Library/Headers   -Wl,--enable-auto-import 
> -shared-libgcc -fexceptions -fgnu-runtime 
> -L/home/Nil/GNUstep/Library/Libraries 
> -L/mingw32/GNUstep/Local/Library/Libraries 
> -L/mingw32/GNUstep/System/Library/Libraries -lgnustep-gui -lgnustep-base
>  -lobjc -lws2_32 -ladvapi32 -lcomctl32 -luser32 -lcomdlg32 -lmpr 
> -lnetapi32 -lm -I. -lPDFKit >&5
> makes too many compile errors(so omitted)
> -----------------------------------------
> exchanging "conftest.c" into "conftest.m" makes no error.
> configure script may need changes. Does any suggestion?
> (PS) Building PDFKit needs 'make LDFLAGS="-lgdi32"' at MSYS2/MINGW32.
>      Building libobjc2 needs "-lpthread" CMakeCache.txt at MSYS2/clang.

is there a way to tell configure that the output should be .m instead of
.c ?
I believe this test is done in a macro and the output file auto-generated.

Files with obj-c content should be indeed called .m, apparently it helps
the compiler to select the correct mode.

I'd gladly improve that.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]