Hi Ryan Yes that works just fine.
I'm sorry that you've had so much trouble so far, but you're not alone - I run into problems all the time and spend many hours making sure I can at least compile GNUstep/Etoile for those modules from time to time, and working with David to get them resolved. Its especially tricky considering you need to use the SVN LLVM/clang. Its also important to note that David Chisnall (the Objective-C compiler maintainer at LLVM for the GNU runtimes) only uses FreeBSD, not Linux. This means that alot of Linux-only defects, which cannot be reasonably anticipated due to the archaic aspects of Linux (or any other platform for that matter) and the fast development pace of LLVM, creep into the compiler which affect the output of GNUstep/Etoile source code files. Good luck! Chris On Tue, 02 Aug 2011 18:41 -0500, "Ryan Harter" <[email protected]> wrote: Hi Chris- Thanks for the info. That's kind of what I was thinking might be needed. To do that do I just go into each of those projects and do a "make" and "make install"? Since they are all covered under the main project I wasn't sure if it was set up that way. Thanks again, Ryan On Aug 2, 2011, at 6:34 PM, Christopher Armstrong wrote: Hi Ryan It might be an idea to try and compile only certain Etoile modules for now, as much of the stuff there doesn't get as much attention as a few key parts. I'd strongly recommend tracking down and playing with: * EtoileFoundation * EtoileUI * LanguageKit before looking at other sections. You should also compile and install EtoileSerialize, UnitKit and the document generation tool before you install these. As a occasional developer, I don't really work with much else inside the Etoile repository, which have never worked satisfactorily for me (except ProjectManager, which at the moment is only a less-than-basic window manager) . Cheers Chris On Tue, 02 Aug 2011 09:18 -0500, "Ryan Harter" <[1][email protected]> wrote: Those of you that are regulars on the list probably recognize me by now. I've been working on getting Etoile compiled for a while now. I've talked to Greg at GNUstep about the same issues on their side, the high barrier to entry that is, and he agreed that it was an issue and suggested that I mention something here. I don't want to just complain, and I certainly don't want to give the impression that I don't think you guys are doing some really cool things, as that wouldn't be very productive. That's why I've been taking detailed notes the whole way through so I can attempt to write (or add to the existing) documentation with version numbers, compile flags, etc, to make the process easier for others. Eventually I'd like to get past that and into helping out on the Frameworks/Apps. I've been following the instructions on the web site, and learning lots of required minor tweaks along the way, but still need some help on two main issues. First of all, and this could be that I have some weird version of sudo, the -E flag on sudo doesn't seem to work for me. I get complaints about GNUstep tools not being in my path. That's not a big deal, I just open a new terminal, sudo -i, source the GNUstep scripts, and leave it up for all of my 'make install's. man sudo shows: -E The -E (preserve environment) option will override the env_reset option in sudoers(5)). It is only available when either the matching command has the SETENV tag or the setenv option is set in sudoers(5). Perhaps I don't hav the setenv option set in sudoers, I'll check later. Secondly, I've installed GNUstep and libobjc2 exactly as instructed (several times). I've compiled and installed GNUstep make, compiled and installed libobjc2, recompiled and installed GNUstep make so that it builds with libobjc2, then compiled and installed the rest of the GNUstep components. I've even tried recompiling and installing llvm/clang after having libobjc2 installed. Still, once I get to running make in Etoile, I get through most projects, then I get this: Making all for subproject bindings... Compiling file poppler_objc.m ... g++: poppler_objc.m: Objective-C compiler not installed on this system make[5]: *** [obj/bindings.obj/poppler_objc.m.o] Error 1 make[4]: *** [internal-subproject-all_] Error 2 make[3]: *** [bindings.all.subproject.variables] Error 2 make[2]: *** [PopplerKit.all.framework.variables] Error 2 make[1]: *** [internal-all] Error 2 make: *** [internal-all] Error 2 I'm not sure why clang thinks there isn't an Objective C compiler installed. Is that even clang? I noticed the line starts with g++. Do I have to set an environment variable, in addition to CC, to tell the system to use clang instead of g++ as well? I was briefly able to get past this, but somewhere in my recompiling the workaround escaped me. So much for my detailed notes :) Thanks again for all of your help, Ryan _______________________________________________ Etoile-dev mailing list [2][email protected] [3]https://mail.gna.org/listinfo/etoile-dev -- Christopher Armstrong carmstrong ^^AT^ fastmail dOT com /Dot/ au _______________________________________________ Etoile-dev mailing list [4][email protected] [5]https://mail.gna.org/listinfo/etoile-dev _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev References 1. mailto:[email protected] 2. mailto:[email protected] 3. https://mail.gna.org/listinfo/etoile-dev 4. mailto:[email protected] 5. https://mail.gna.org/listinfo/etoile-dev -- Christopher Armstrong carmstrong ^^AT^ fastmail dOT com /Dot/ au
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
