[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Portable toolchain
From: |
Kevin Ingwersen |
Subject: |
Re: Portable toolchain |
Date: |
Thu, 28 Nov 2013 02:26:01 +0100 |
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 <ivan@vucica.net>:
> 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 for this mailing list.
>
> What I have described above is what I think I have done with non-GNUstep
> MinGW a couple of years ago. I have never done it with GNUstep's distribution
> of MinGW and I have never used it in combination with GNUstep's build system
> gnustep-make or any other component of GNUstep.
>
> Try whether what I described above works with C, then try writing a program
> using Objective-C and GNUstep. If something breaks down, let us know, and
> someone can perhaps try taking a closer look. Right now, considering your
> posts are a bit unclear, we can mostly encourage you to explore this yourself
> until you figure out what are the issues that we can actually help you with.
>
> Thank you for your interest in GNUstep!
> Thank you for trying to encourage your teachers to consider using C,
> Objective-C and GNUstep!
>
>
>
> On Tue, Nov 26, 2013 at 11:29 PM, Kevin Ingwersen <ingwie2000@googlemail.com>
> wrote:
> Hey.
>
> Of course I know they are not equivalent. :p
>
> well what I would like to basically do is, have a zip containing the build
> environment, which can be extracted anywhere, and using a .bat file, the
> currently running shell would be set up to „use“ the environment.
> I have that setup on Mac OS already. And I would like to have a similar on
> Windows. That way I can:
> - Save time finding/downloading the right toolchain. Because i can just copy
> it somewhere save, like on a backup drive, and everything is fine.
> - Use the toolchain anywhere from a USB dongle. Especially important when
> having no access to my own maschine, but still need a compiler.
> - A reusable toolchain that I can give to other people or redistribute as
> „portable“.
>
> maybe that explains what I ment. ^^;
>
> Kind regards!
> Am 26.11.2013 um 23:14 schrieb Markus Hitter <mah@jump-ing.de>:
>
> > Am 26.11.2013 20:37, schrieb Kevin Ingwersen:
> >> I really like C++ and also the concept of ObjC++. And that brought me
> >> here. [...] because the teachers have the books for C
> >
> > Just a side note: C != C++ != ObjC != ObjC++
> >
> > To allow following your words better it's probably a good idea to be a
> > bit more precise of which of the four languages you're talking.
> >
> >
> > Markus
> >
> > --
> > - - - - - - - - - - - - - - - - - - -
> > Dipl. Ing. (FH) Markus Hitter
> > http://www.reprap-diy.com/
> > http://www.jump-ing.de/
> >
> > _______________________________________________
> > Discuss-gnustep mailing list
> > Discuss-gnustep@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>
>
>
> --
> Ivan Vučica
> ivan@vucica.net
- Portable toolchain, Kevin Ingwersen, 2013/11/26
- Re: Portable toolchain, Riccardo Mottola, 2013/11/26
- Re: Portable toolchain, Markus Hitter, 2013/11/26
- Re: Portable toolchain, Kevin Ingwersen, 2013/11/26
- Re: Portable toolchain, Ivan Vučica, 2013/11/26
- Re: Portable toolchain,
Kevin Ingwersen <=
- Re: Portable toolchain, Fred Kiefer, 2013/11/28
- Re: Portable toolchain, Kevin Ingwersen, 2013/11/28
- Re: Portable toolchain, Fred Kiefer, 2013/11/29
- Re: Portable toolchain, Kevin Ingwersen, 2013/11/29
- Re: Portable toolchain, Riccardo Mottola, 2013/11/28
- Re: Portable toolchain, Kevin Ingwersen, 2013/11/28