> >
> > It is Makefile file problem
>
> Err, what do you mean?
I meant just you say:
make linuxegcs
no ROOT Win32 should be exposed / involved into the build process.
All header files must be from Cygwin / gcc only.
> What I did when I tried to compile ROOT using
> Cygwin GCC was to take Makefile.linuxegcs and use that (following
> Fons' suggestion back ages ago). However, I soon saw errors like
> "implicit declaration of unknown function ..." and later "unresolved
> reference to ...".
>
> Now looking through the code then I basically saw no problem with
> Makefile.linuxegcs under Cygwin, though I did have to change a few
> preprocessor things in the CINT sources.
At this point NO VC++ header file should be involved.
> I got as far as compling and linking cint and makecint - as far as I
> remember - but rootcint defently failed to link.
> Now I really don't believe that it's a Makefile problem. Rather, it's
> a source code problem, 'cause for a great many things, you want to use
> the Unix source code, and for a tiny piece you'd like to use the Win32
> source code (Win32 graphics rather than X same), but there was no
> obvious way that could be achived by only setting preprossor flags in
> the Makefile - source code changes is needed, probably both in CINT
> and ROOT.
Makefile and Cygwin must hide WIN32 completely and no WIN32 must
be involved. If it is not case it is "Makefile" problem.
Sorry can not say more since I did not try that option myself.
> According to the GPL, it's enough to provide a pointer, like
>
> You need <a href="http://www.cygwin.com">Cygwin</a> installed on you
> machine.
>
> Bloody close to saying:
>
> You need a C++ compiler installed on your machine.
One needs no C++ compiler and no Cygwin installed to run ROOT
That's the point.
> or even,
>
> You need an Operating System installed on your machine.
I did see problem (at least with the Red Hats). Very often one does
need to say "you need Operating system Red Har xxxx installed"
to run my binary. Very few things will work with no re-compilation.
It is not case under Windows.
> See, really no problem in that :-)
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:46 MET