[Omake] Cygwin toolchain using standard win32 install
Andrew Gacek
andrew.gacek at gmail.com
Tue May 29 10:27:53 PDT 2007
Running "omake --configure" fixes the issue. But then if I run "omake
--configure" from within a different project directory (which uses
Win32 rather than Cygwin) will these settings again be lost?
-Andrew
On 5/29/07, Aleksey Nogin <anogin at hrl.com> wrote:
> On 29.05.2007 10:18, Andrew Gacek wrote:
>
> >> Note that as long as you set OSTYPE before opening any files (including
> >> build/Common and build/C), then you do not need to also mess with
> >> GCC_FOUND/YACC/LEX/EXE/etc - as long as you set OSTYPE early enough, all
> >> those will follow automatically.
> >
> > Right now I have
> >
> > if $(equal $(OSTYPE), Win32)
> > OSTYPE = Cygwin
> > GCC_FOUND = true
> > GXX_FOUND = true
> > export
> >
> > as the very first lines in my OMakeroot file. After these lines I open
> > build/C and build/OCaml. But if I leave out the GCC_FOUND = true I
> > get,
> >
> > *** omake: reading OMakefiles
> > *** omake error:
> > File c:\Program Files\OMake\lib\omake\\build\C.om: line 96,
> > characters 21-33
> > unbound variable: GCC_FOUND
>
> What happens if you run "omake --configure"?
>
> --
> Aleksey Nogin, Research Scientist
> Advanced Technologies Department, Information & System Sciences Lab
> HRL Laboratories, LLC, Malibu, CA
> _______________________________________________
> Omake mailing list
> Omake at metaprl.org
> https://lists.metaprl.org/mailman/listinfo/omake
>
More information about the Omake
mailing list