MapServer and Borland C++

[Daniel Morissette]

Hi,

Back to the question of whether MapServer can be compiled with the
Borland compiler:  I withdraw what I wrote in my previoyus message...
it's probably not that simple.

I got the Borland C++ 5.5 command-line compiler (available as freeware
from the Borland web site in case anyone is interested!) and did a
couple of quick tests.  Adapting the makefiles was not too bad, but I
stopped when I started getting errors in the project.h (PROJ.4) header
file.  Which implies that there would also be work required in some of
the modules that MapServer uses before we can compile MapServer itself
with Borland.

Since it's not a trivial task, I think I'll give up for now.  However,
I'm wondering if there is enough interest to justify supporting the
Borland compiler???

-- 
------------------------------------------------------------
 Daniel Morissette                       danmo at videotron.ca
              http://pages.infinit.net/danmo/
------------------------------------------------------------
  Don't put for tomorrow what you can do today, because if 
      you enjoy it today you can do it again tomorrow.


Daniel Morissette wrote:
> 
> Lyndon Zimmermann wrote:
> >
> > I looked at compiling the package under NT, but I only have access to Borland
> > C++ Builder and did not feel like trying to port the MapServer installation
> > across from a the Microsoft VC++ instructions provided.
> 
> Lyndon,
> 
> Have you tried using the makefile.vc with Borland?  The MapServer code
> itself (not talking about the optional modules such as Freetype, etc.)
> is very clean C code that should compile with most compilers without too
> many problems.
> 
> So the main problem may be to use the makefile.vc with Borland.  I am
> not familiar with Borland C++ Builder, but it should have some way to
> deal with makefiles... and surprisingly enough, Microsoft's makefiles
> are not that different from the Unix ones (for once Microsoft didn't
> reinvent the wheel!), so I would expect that it should not be hard to
> adapt the makefile.vc to work with Borland.
> 
> Of course Cygwin may not be a bad solution but I can't tell since I
> haven't used it myself.  However I would hate to think that by providing
> only MSVC++ makefiles we have encouraged the Micro$oft Monopoly... it
> was really not the intention, and I would be happy to help supporting
> Borland if I had access to it.
> 
> Just my 0.02$ (CDN$ :)
> --
> ------------------------------------------------------------
>  Daniel Morissette                       danmo at videotron.ca
>               http://pages.infinit.net/danmo/
> ------------------------------------------------------------
>   Don't put for tomorrow what you can do today, because if
>       you enjoy it today you can do it again tomorrow.