nice list of JVM's - very handy !
I think we're getting into the area of users versus developers. If the developers don't have the resources or skills to maintain the make system then it will get left behind - no matter what we say here. And that appears to be happening now. If a user tries the code and has issues with the make files then I understood the Open-source mentality was that the user should become a developer - at least to maintain the scripts which only they use. Have I misunderstood?
Perhaps we should do a poll on the users list to see if this is really an issue or whether we are making it one out of thin air?
| "Lilantha Darshana"
<[EMAIL PROTECTED]>
31/03/2005 20:03
|
|
FYI: here is a list of operating systems that have jvm 1.4.x supports.
Sun jre: http://java.sun.com/j2se/1.4.2/system-configurations.html
IBM jre: http://www-128.ibm.com/developerworks/java/jdk/index.html
Hp jre: http://h18012.www1.hp.com/java/alpha/index.html
JREs for other OSs: http://java-virtual-machine.net/other.html
These are a small percentage of all the operating systems today we have.
And even for them jre versions for some of them are still 1.1 or 1.2.
But not 1.3.x or 1.4.x
Good examples are widely use operating systems like:
NetBSD and OpenBSD JRE versions are still 1.1 or 1.2.
In some of the cases the same OS in different h/w architecture does not have JREs.
In contrast, most of UNIX flavors carry Make with some C/C++ compiler than that of a
JRE. Since Unix flavors are written in C for the h/w.
So having Make/GNU Make scripts facilitate compiling Axis C++ on such OSs and aid porting
Axis C++ into such platform with a less effort.
This is a general thought with thinking in the line of project future support for other OSs.
If you all think this is difficult to be finished for 1.5 we’ll plan to do it in 1.6. if so, we need
updating our build instructions in documentations, to state that we do not support make in
1.5 release??
I’m giving +1 for at least to maintain Ant and Make. We can avoid maintaining MSVC projects though.
thanks
-Lilantha
From: John Hawkins [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 31, 2005 3:37 AM
To: Apache AXIS C Developers List
Subject: RE: GNU Make and VC++ projects for 1.5 release
I think that's the point I'm afraid - it is a pain and no one is updating them :-(
I can't believe there are any platforms out there without JVM support? We've got this working on OS400 - what else is worse?
| "Lilantha Darshana"
<[EMAIL PROTECTED]>
30/03/2005 15:27
|
|
My belief is that we need having GNU make file maintained to support
systems that do not have jvm support. There are still lot of Operating
Systems that do not have JVM support but some flavor of 'Make' support
is.
Visual Studio project are really good on developing with an IDE support.
Hence, we need keeping them to make ppl productive. I assume most of us
use MSVC IDE compare to emacs/KDevelopment or other IDEs.
Hence, +1 to keep all three type of files if really not a pain.
thanks
-Lilantha
-----Original Message-----
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 29, 2005 12:02 PM
To: Apache AXIS C Developers List
Subject: GNU Make and VC++ projects for 1.5 release
Hi All,
As I understand, the above are out of date.
Are we going to fix those before 1.5 release?
Thoughts please...
Thanks,
Samisa...
_______________
Attend Siebel User Week in Barcelona, April 17-20, 2005
Visit www.siebeluserweek.com/europe
This e-mail message is for the sole use of the intended recipient(s) and contains confidential and/or privileged information belonging to Siebel Systems, Inc. or its customers or partners. Any unauthorized review, use, copying, disclosure or distribution of this message is strictly prohibited. If you are not an intended recipient of this message, please contact the sender by reply e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation.
_______________
Attend Siebel User Week in Barcelona, April 17-20, 2005
Visit www.siebeluserweek.com/europe
This e-mail message is for the sole use of the intended recipient(s) and
contains confidential and/or privileged information belonging to Siebel
Systems, Inc. or its customers or partners. Any unauthorized review, use,
copying, disclosure or distribution of this message is strictly prohibited.
If you are not an intended recipient of this message, please contact the
sender by reply e-mail and destroy all soft and hard copies of the message
and any attachments. Thank you for your cooperation.
