[Coin-discuss] BCP and Windows

[Stephan Hennig]

Brady Hunsaker schrieb:

> On Fri, 2003-10-31 at 08:39, Stephan Hennig wrote:
>> 
>> As the very first problem BCB can't find <unistd.h> on line 11 in 
>> file CoinHelperFunctions.hpp. There is no such file on my machine. 
>> I can hear you laughing, but I have no idea how simple/complicated 
>> that problem is.
>> 
>> Is there any hint to what problems would/could/should raise up and 
>> have to be dealt with. What were the critical files when doing 
>> adjustments to make COIN run with MSVC++ (which is no option for 
>> me)?
>> 
>> Has really no-one tried BCB before (with a little more system 
>> knowledge)?
>> 
> 
> I'm pretty sure no one has communicated with the list about efforts 
> to compile COIN-OR software using Borland.  There have been 
> successful efforts to compile COIN-OR code under MS Visual C++, 
> however.  On the assumption (??) that Borland and MSVC++ are somewhat
>  close,

I suspect there are worlds between them. :(

> you could try adding the line #define _MSC_VER before even the
> include files.

This is old hat for an old crack as me. ;) I tried it just before you
received my personal mail. When doing so, bcc stopped at
CoinHelperFunctions.hpp line 428 which reads
  srand(jseed);
At that point I quit, because I had no idea about what i did when
defining _MSC_VER. That's why I didn't mention it.


> This is used in some places in the COIN-OR code to handle 
> compatibility issues, including the <unistd.h> problem.  Whether or 
> not this helps depends on whether MSVC++ and Borland code is easily 
> interchangeable.  I have no idea whether or not that is true.
> 
> Unfortunately, BCP is complicated enough that I will be (pleasantly)
>  surprised if this is sufficient.  You can search for "_MSC_VER" in 
> the code to find the places where there have been issues in the past,
>  if you are willing to try to adjust them for Borland.  It's possible
>  there will be new issues as well.

Ok, that's very valuable, because now I know I'm on the right way.
I'll try my very best although I'm somewhat frightened when faced with
compiler issues. As a first result (now after a couple of hours)
CoinWarmStartBasis.obj compiled. :)


> I do hope that we will make more efforts to support Windows in the 
> future, but even then, I expect that we will target support for 
> open-source compilers, such as gcc under cygwin, or MinGW.

Is this list open for questions concerning compiler issues in
conjunction with coin? Or is this a waste of (your) time? Again, I'm not
an expert system programmer.

Kind regards,
Stephan Hennig