| Being OS agnostic is wonderful! I'm doing my best to, where practical, write and use software that I can find on as many platforms as possible. (Which is one of the reasons why I'm so interested in GNUstep.)
But, as you know, operating systems themselves are not operating system agnostic, and we're lucky to even have so many cross-platform environments. So, setup is certainly going to differ between platforms, including operating systems, build environments, etc.
So when asking questions that have to do with setup of a complex set of libraries such as GNUstep, especially if you're only starting with the tool you're asking about, it's best to focus on a single platform and specifying it in the question. :-)
Good luck! Hi Ivan,
thanks for the very complete answer.
I did not state the operating system, because usually I am operating system agnostic,
as I just use whatever our customer require.
Thanks once again,
Paulo
On Thu, Aug 23, 2012 at 6:58 PM, Ivan Vučica <ivucica@gmail.com> wrote:
You have not mentioned which operating system you use. Everything I'm about to say has been tried primarily under Ubuntu (and a few years ago under Debian). Other UNIX-based systems probably also fit, but I have absolutely no idea about Windows.
Building everything from source code is the safest method, as far as I'm concerned. I build everything: the compiler, the runtime, and various GNUstep libraries. I use latest development repositories for each.
Take a look at the script and the notes here: Just as the repository's name implies, this script is intended for use with Ubuntu (but I see no reason why the compiling part would fail under other UNIX systems. Debian is also probably going to play nicely). More specifically, this script has been tested with Ubuntu 12.04.
Take vanilla Ubuntu 12.04, run the script, and in an hour or so, you should have a compiler (clang), a runtime (libobjc2) and the libraries (GNUstep) up and running.
You may want to read the script and decide which lines you want to put on the bottom of your ~/.bash_profile. For example, I have these ones there:
export PATH=$PATH:$PWD/Release+Asserts/bin: # llvm/Debug/bin contains the clang binary
export CC=clang # Make Clang the C/ObjC compiler rather than GCC
. /usr/GNUstep/System/Library/Makefiles/GNUstep.sh
Additionally, you may want to save time if you don't want to compile clang. I personally do. If you don't, just "apt-get install clang", and feel free to edit the script removing the portions that deal with llvm and clang.
Good luck!
--
Ivan Vučica - ivan@vucica.net
|