Hello again,
You probably realized it is not the first attempt
to use CYNGUS. This had been discussed.
You may go to http://root.cern.ch/root/Search.phtml
type "Cyngus" and find this matter was discussing in 1997.
click "Search".
For example one may find there a message
( Fri, 11 Jul 1997 13:15:00 +0100 ) telling:
".. In fact you are asking us not static libraries but g++ compiled
code under Win32. It had been discussed already. We have no manpower
and will to do this, but we do provide our source and allow everyone
to compile his own version with his favorite tool too.
I hope ROOT team will be not against to include your correction in
our code too as soon as it doesn't destroy our supported platforms
... "
>
> Where I need help is what to do with the `THREAD_*', `WIN32_*' and
> `WINNT_*' files. What libraries are these source files a part of? In
> what order do they appear on the link line? Also, are any of these
> source files and/or libraries conditionally built under different
> circumstances?
>
Actually I've replied with another message. I have no idea about THREAD
Very likely it is a TThread implementation.
My guess it was tested under UNIX only.
> As I mentioned, the actual implementation of how to invoke the compiler,
> linker, etc. is taken care of by GNU Libtool. I just need to know the
> higher-level project structure or ROOT under Win9x/NT.
>
> > But I don't like an idea to force Windows people to install CYGNUS
> > tools (i.e. UNIX layer) on the top of the WIN32.
>
> Many people might feel the same way about being "forced" to install a
> commercial compiler suite (e.g. Microsoft Visual Studio, street price
> $900 US) before they can build ROOT on their WinNT computers.
Apparently we shopping different way. Of course there is no means to buy
the entire Developer Studio (especially on the street).
"Visual Studio 6.0. Professional edition" includes:
1. Visual Basic
2. Visual C++
3. Visual FoxPro
4. Visual InterDev
5. Visual J++
6. + 3 CD of the MS knowledge base known as MSDN
The price about 200 dollars (I can check it latter)
Visual C++ v.6.0 includes
1. Visual C++ v.6.0
2. Windows NT Workstation v.4.0
3. + 3 CD of the MS knowledge base known as MSDN
cost STAR at BNL 85 $
MS Web site http://www.microsoft.com/products/prodref/lists/us_aerp.htm
says:
Visual C++ Standard
Visual C++ Std 6.0 Win32 AE
Version: 6.00
Part Number: 254-00050
Estimated Price: $44.95
Environment: 32-Bit Win
Media: CD
Visual C++ Std 6.0 Win32 License Pak AE
Version: 6.00
Part Number: 254-00057
Estimated Price: $24.95
Environment: 32-Bit Win
Media: Non-specific
> Actually, GNU Autoconf recognizes and can use third party compilers,
> e.g. the Microsoft C/C++ compiler. The user can chose which compiler to
> use at build time.
>
> Currently, WinNT users must install the following to build ROOT on their
> own:
>
> 1) CMZ
> 2) Microsoft or Borland compiler
>
> With the Autoconfed version of ROOT, users would only have to install
>
> 1) cygwin
>
Ok, nobody against. Even more I will be very happy somebody will fulfill
this job.
> Of course, users could still install and use, e.g. Microsoft Visual
> Studio if they wanted to.
>
> You can look at the cygwin package as adding a UNIX layer on top of
> Win32 if you wish, but you can also look at it as providing a no-cost
> and complete development environment, e.g. `make' and the C, C++ and
> Fortran 77 compilers. The user doesn't have to use the "UNIX layer" if
> they don't want to.
Yes that's what I said myself. I took GNU make source directly from
ftp://prep.ai.mit.edu
and built the beautiful GNU make with no CYGNUS.
Again I shall be very happy somebody builds ROOT with entire CYGNUS
tool but all the current compilation / linker flags are for MS Visual C++ though.
They are no use for CYGNUS. From this point of view your task is becoming
even simpler. You need no "know-how" from ROOT.CMZ at all. It doesn't help
anyway.
> However, it is nice
> to be able to give users the choice, as the commercially available
> development environments are quite expensive, particularly for the small
> university research groups.
Hmm, It seems to me the "learning version Visual C++" is less then 44 dollars.
Reading this discussion has cost them more I guess.
Very likely your price is from Europe I don't know that.
From another hand CYGNUS is not free for commercial companies too.
The page: http://sourceware.cygnus.com/cygwin/licensing.html
says: "
Cygnus' Native Win32 GNUPro product includes a commercial license for
Cygwin that is more suitable for commercial use of the Cygwin library.
Contact info@cygnus.com for more information about this license. . . "
>
> > The same "know-how" one can find in the "Imake rules" those CERN uses
> > to create makefiles to build CERNLIB for Windows NT.
>
> As I mentioned, it is not the compiler flags, linker flags, etc. that is
> important. We need the ROOT specific list of libraries, and the source
> files that go into these libraries. That's all.
I guess I've given you some information on that.
>
> Valery, thank you for taking the time to answer my e-mails with your
> thoughtful answers to my questions. I hope I don't seem combative about
> the GNU tools vs. the commercially available tools.
Never mind but I have some experience. For many years I have been watching
CYGNUS and many other companies (free and not free) activities. Time by time
I am picking their products to trial. I hope I have some ground making statements.
For example 7 years ago the best developer environment for MS DOS was DJ Delorje
implementation of gcc compiler. It is still the best product for MS DOS.
(see http://www.delorie.com/) The CERNLIB for MS DOS was done very with this
environment. If today we were discussing what compiler should we choose to port
ROOT under MS DOS my advice would be DJ Delorje not Microsoft. So I have no
intention to discuss GNU vs MS or something like this.
We are discussing ROOT.
Valery
This archive was generated by hypermail 2b29 : Tue Jan 04 2000 - 00:43:31 MET