Re: I think - Remove Microsoft from Installer Pages

[Johnny Kewl]

----- Original Message ----- 
From: "Nathan Beyer" <[EMAIL PROTECTED]>
To: <dev@harmony.apache.org>
Sent: Monday, March 03, 2008 3:22 AM
Subject: Re: I think - Remove Microsoft from Installer Pages

If you can get everything massaged to compile on VS2008 or VS2005,
we'd certainly take a serious look at it. The current state of affairs
isn't a statement of any sort, it's just what we've come to so far.
The community drives development, so it's just a matter of getting the
community interested and motivated.

Ha ha... how many years has it taken already...
I'm thinking here... versions are been released right... they target windows 
32 and 64 bit right.
Why dont we just ask the guy/gal that is compiling the windows stuff up, how 
they do it?
They must be using a recent compiler... and for 64 bit its probably a 
current windows release.
I'm thinking there are two versions of this project? .... we just got to 
find the other one ;)

I'm thinking maybe there a cold war going on ;) I can act as a go between, 
we from Africa and have
one foot in Russia, one foot in the USA and the rest dangling in the 
atlantic ;)
The more I think about it, the more I'm sure its been done already... makes 
one wonder hey ;)

-Nathan

On Sun, Mar 2, 2008 at 6:18 PM, Johnny Kewl <[EMAIL PROTECTED]> wrote:

 ----- Original Message -----
 From: "Nathan Beyer" <[EMAIL PROTECTED]>
 To: <dev@harmony.apache.org>
 Sent: Monday, March 03, 2008 12:34 AM
 Subject: Re: I think - Remove Microsoft from Installer Pages


 > There are plenty of places that still sell VS.NET 2003 -
 > 
http://www.google.com/products?hl=en&hs=XOH&resnum=0&q=visual+studio+2003&um=1&ie=UTF-

 What do you know... and its not even listed on the MS site anymore ;)
 I still think this is a problem waiting to happen anyway... also hard to
 convince a company that
 just licensed 2008 to go back and license 2003.... no there has to be a
 better way.
 Somehow find a way to bring MS developers in line with the Linux guys... 
so
 they can work in
 Harmony ... ha ha

 I've just had a good look at Cygwin... no, because it creates 
dependencies
 on its dlls, and java
 still lives outside on the MS systems so /linux to c:\ path conversions
 would drive people mad...
 So cygwin is out I think....

 I think it all really comes down to finding a GCC compiler that likes
 windows and can interface with
 an decent IDE... the MS dudes will be happy.
 Havnt quite given up yet... for me getting the code to the developer is
 going to be much easier than
 trying to get the devloper onto linux.... so I'm trying.

 Dont worry I'm not blaming you... I can see the MS has forked off at a
 tangent (again!) ha ha
 ... but there is a problem...




 > -Nathan
 >
 >
 > On Sun, Mar 2, 2008 at 3:04 PM, Johnny Kewl <[EMAIL PROTECTED]> 
wrote:
 >> Guys, I think you need to make an explicit note on the installer 
site...
 >>  CANNOT BE COMPILED ON WINDOWS
 >>
 >>  The problem is the MS tools have moved on... 2003 cannot be found.
 >>  There seems to be a massive change on 2005 and up compilers.
 >>  Just about everything is deprecated, the headers seemed to have 
changed
 >> alot from linux compilers.
 >>  Or more simply... VS is now windows only.
 >>
 >>  I've being trying from the ant builds and also from VS 2005 
directly...
 >>  You literally have to rewrite the code...
 >>
 >>  I see the Sun JVM does also not support development on the MS 
platform,
 >> whether that is strategic or
 >>  a technical issue as well, I'm not sure, I think its the former.
 >>
 >>  I'm not up on all the compilers but from googling, there does not 
seem
 >> to be a compiler that one
 >>  can readily use on MS.
 >>
 >>  If you want to attract developers in this market... you have to show
 >> them how to do it, or find an
 >>  old MS compiler and stick it on a FTP server or something.
 >>
 >>  We going to setup a linux dev environment for this, but that 
immediately
 >> reduces my local skills to a
 >>  grand total of one ;)
 >>  Possibly Cygwin is the way to go... I know that can tie up with
 >> netbeans, but I'm not sure about
 >>  eclipse.
 >>
 >>  Its a massive project... if the user cannot get it to their familiar 
dev
 >> environment... it becomes a
 >>  1 month excercise to just get going...
 >>  The divergence in tools is throwing away a huge developer market... 
very
 >> unfortunate.
 >>  Sorry... I just cant figure out a way to get it going... and if we 
do
 >> port it to MS tools, it will
 >>  never be compatible again with the CVS.
 >>  ... snookered ;)
 >