Board index » kylix » Avoiding Linux hell

2003-11-18 08:53:04 PM
kylix1
Hi,
I will start a delphi/kylix project where I should avoid the "Linux hell", i.e, must
be compatible with the larger linux distribution possible.
This seems nearly impossible, but...
What is that problem?
What should I avoid to do?
Is there any special code treatment I should be aware of?
What if I stick to the same kernel version?
What if my application is a Console one (as opposed to GUI)?
Any thoughts?
Clément
 

Kostya
 

Clément Doss wrote:
freeware/open source sites for updates to the Kylix bugs and updates to
support newer glibs and QT libs.
We use Java, therefore, not a problem <G>.
run ok here, but you could encounter glibs problems, if you are oding any
data access.
The best thing you can do (IMHO), is to use one of the above. BuilderX would
do the console job for you, since it can use different compilers and
therefore does not suffer from the non update woes that hurt Kylix.
 

{smallsort}

"Clément Doss" < XXXX@XXXXX.COM >wrote in message news:3fba07d4$ XXXX@XXXXX.COM ...
www.linuxbase.org/
 

-Michael
 

Michael Schnell wrote:
are today). Prorprietary Microsoft's NET version and Mono's version are
not totally compatible. Go to the mono site and check it out in the FAQ
section. MS.NET <>Mono.NET.
Of course if Mono NET is not too far off from a final delivery date, using
MONO NET on both Windows and Linux/Unix might be an option. I do wonder
however, why you have to wait until sometime in the future to develop
something, when it is not necessary <G>.
 

Delphi for .NET should issue warnings when you use non portable
features. If you don't get warnings you should be save. Of course, if
you need anything supported on only one platform or that is implemented
differently in the .NET environments available, you need to take care of
that and deploy multiple versions. But the basic "business logic" should
be portable.
OTOH I suppose this is true for C, Python, Java, too.
ported to .NET (and thus to Linux) using Delphi for .NET, while the hope
for doing this with Kylix is delayed at least <g>.
-Michael
 

"pNichols" < XXXX@XXXXX.COM >wrote in message
Mandrake, and Linux du jour.
 

Clément Doss wrote:
progressing steadily towards the 2.0 version. The beta version already has
almost all the Delphi features and some extras as operators overloading,
static fields...
It already runs on Linux and FreeBSD, and it seems that more platforms will
be supported with the final 2.0 release
Ciao, Dean
 

JQP wrote:
correctly? I do not have any problems with Java running on any of the
distros, nor with Python, nor Perl.
If you are referring to Kylix, yes there was a problem, due to the Winelibs
and Borland not keeping up with current distros. I doubt that Novell (who
nows owns Mono), will have the same problems, since they now own the de
facto USL Linux Distro.
 

Michael Schnell wrote:
portable. But even the WinForms are not. I would check the Mono site first,
before I hedged my bets on a smooth transition.
large consortium that MUST adhere to the standards. That is the problem
with DOT.NET. You have a company who owns the patents and licenses who is
noted for making everything proprietary. Mono is creating a clean room
version of NET.
Mono is not MS certified and I would seriously doubt it would ever be. They
cannot submit their standards to MS, nor can they obtain the MS code
specifications, because MS will give these to no one <G>.
This is totally different than C, Perl, Python, and Java. All of these are
tightly monitored and standards and source code are released to all who are
a part of the process.
from Borland about how they plan to make this work, if you seriously need
xplatform support.
 

"pNichols" < XXXX@XXXXX.COM >wrote in message
Consistency and compatibility across Linux are what's needed. And without
too much lost efficiency or added complexity.
 

"pNichols" < XXXX@XXXXX.COM >wrote in message
have a technology equivalent to java, but completely free (as in freedom).
It made sense to build on MS's work to do that.
 

JQP wrote:
I am aware of.
If you really need XPlatform and desire only Pascal, why not use the Pascal
for JVM?
Component Pascal for the JVM (can use the Eclipse IDE)
www.citi.qut.edu.au/research/plas/projects/cp_files/cpjvm.jsp
Also available is Cantebury Pascal for JVM
www.webcom.com/mhc/pas3release.html
 

Byoob wrote:
approval. Of course, you are free to clone anything (just as MS cloned Java
with NET), but you cannot directly integrate with MS' code.
I understand Mono's goal is compatibility, but real compatibility will make
Mono lag behind NET for years.
why not use Java instead, which is available now? That is what I do not
understand.