gnustep-dev
[Top][All Lists]
Advanced

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

Re: compiling GNUstep on OpenBSD - various compiler/runtime options


From: Riccardo Mottola
Subject: Re: compiling GNUstep on OpenBSD - various compiler/runtime options
Date: Sat, 4 Jan 2020 22:53:58 +0100
User-agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0

Hi,

On 2020-01-03 10:07, Sebastian Reitenbach wrote:
The gnustep packages use option 4, you may look into gnustep.port.mk and the 
respective packages makefiles. Libobjc is installed as libobjc2. Linker is 
ld.bfd. Libobjc2 is still only 1.8, a few packages had build issues and others 
runtime issues when I tried to upgrade to libobjc2 2.0.


With your inspiration, I got a big step forward. I am able to run "ink" now using Option 4) clang + libobjc2 "current".

I needed to

configure make [in Niels fork]:

./configure --prefix=/ --with-layout=gnustep --with-library-combo=ng-gnu-gnu --with-tar=/usr/local/bin/gtar LDFLAGS=-fuse-ld=bfd

(we always have issues with BSD tar, so I just added it.. but what exactly does this bfd linker mean)

re-build cmake, after having sourced GNUstep.sh, using these options:

cmake .. -DBUILD_STATIC_LIBOBJC=On -DTESTS=Off


then reconfigure && reinstall make!


after this, building of the rest of gnustep as just plain configure&make install

the only two "big" differences are that

- I included that bfd linker option

- I did not specify for libobjc2

-DCMAKE_C_COMPILER=clang
-DCMAKE_CXX_COMPILER=clang
-DCMAKE_ASM_COMPILER=clang -DCMAKE_ASM_FLAGS=-c


as suggested in the INSTALL!


Riccardo


Riccardo




reply via email to

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