I can not source the .sh file from within windows’ cmd.exe o.o But I think my installation is broken anyway :/ Once I have fixed my install, how can I boot the built environment?
Kind regards, Ingwie Am 28.11.2013 um 09:11 schrieb Fred Kiefer <[email protected]>: > You should not need to manually fiddle with the GNUstep environment > variables. Just source the GNUstep.sh shell script from the Makefiles > directory. If this has been setup up correctly it should give you a working > environment. > > As for your example, it is basic but wrong. You missed the @ before the > string literal and that is what the compiler is trying to tell you. > > Hope this helps, > Fred > > On the road > > Am 28.11.2013 um 02:26 schrieb Kevin Ingwersen <[email protected]>: > >> I have taken my USB drive with GNUstep installed onto to a friends computer. >> >> After setting up PATH, INCLUDE_PATH, and LIBRARY_PATH, it worked…some. I got >> far enough that it is giivng me the error message that there is „No >> refference to ‚NSLog‘“. trying to use @„…“ produces another error about >> something not being loaded. To be very honest, I havent copied the errors, >> because it was at school. Here is the test programm: >> >> #import <Foundation/Foundation.h> >> int main() { >> NSString *str = „o.o“; >> NSLog(str); >> return 0; >> } >> >> Ultra basic, right? Well, it ocmpiles fine on my mac, but not on GNUstep >> when taken to a different computer. >> >> What environmental variables do the compilers look for? Also during >> installation, a GNUstep folder was created inside the folder I originally >> instaleld my stuff into. Originally, I installed into E:\System - but now I >> also have E:\System\GNUstep - is that normal/ok/safe? >> >> Kind regards, Ingwie >> >> PS: Output on mac: >> >> Ingwie@Ingwies-Air ~/Work/objc $ gcc win.m -framework Foundation >> win.m:4:8: warning: format string is not a string literal (potentially >> insecure) [-Wformat-security] >> NSLog(str); >> ^~~ >> 1 warning generated. >> Ingwie@Ingwies-Air ~/Work/objc $ ./a.out >> 2013-11-28 02:25:08.696 a.out[37953:507] o.o >> >> >>> Am 27.11.2013 um 04:05 schrieb Ivan Vučica <[email protected]>: >>> >>> Kevin, >>> >>> The following presumes you refer to Windows, as you mention that you use >>> .exes in school. You will not be able to share the environment with OS X. I >>> am unable to check the correctness of the direction I am pointing you to, >>> but it might prove to be a good start. >>> >>> How would I approach making a "portable" GNUstep build environment for >>> Windows? I would suggest you first install GNUstep on a Windows desktop >>> where you do have admin privileges, then grab the C:\GNUstep folder and >>> copy it to a stick. Then go to another Windows machine which does not have >>> GNUstep and try running various compiler binaries. They are located in >>> \GNUstep\bin. >>> >>> You will need to familiarize yourself with use of GCC (the compiler), MinGW >>> (the underlying "distribution" of GCC and other tools that GNUstep under >>> Windows is using) and you'll have to figure out how to compile a program >>> using the command line. Sadly, this is out of scope _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
