I second that... it's not really hard to write cross platform c++ code.
You just have to think about it before using platform specific code.
ah may well i would agree with you that if windows used something more standardized like using a main and not a winmain...or even thousands of typedef for a string. Things would be more easier...
But you just have to plan the code before coding it. most of the work of an app isn't platform specific. There is may be just the threads...Input Output, networking and other things like that.
1 + 1 will always be 2 on every platform.
a for loop will do the same thing on every platform. But reading a file may be a bit different. But not enough to say that it is hard. It may be just a bit annoying to do. But i like doing things like that.
Oh and using VM doesn't mean absolutely cross platform.
FlexBuilder 2...a plugin written in java for eclipse only available for Mac and windows. I would really like to know how they made non cross platform code using Java...
Auto package for happy pinguin....
http://autopackage.org/
The fact is that installing from source is a really bad thing. Not that it don't work or it's difficult. But but having file spreaded everywhere is not a good thing. So then package is really great...
One of the thing that would be great is... having the source archive and open it with let say synaptic. then synaptic would find the needed dependencies so it should work and make the sources in a temp directory.
Then when it's done, synpatic do something like make install to install the file in a directory so he would be able to create a package for it. and install it cleanly. And finally putting every sources to trash except the archive.
Then you have something that in drag and drop would build/install a package from source
and having autopackage file for commercial binaries is a damn great idea. It's better than using the ugly.sh script....
Slashdot Mirror
I second that... it's not really hard to write cross platform c++ code. You just have to think about it before using platform specific code. ah may well i would agree with you that if windows used something more standardized like using a main and not a winmain...or even thousands of typedef for a string. Things would be more easier... But you just have to plan the code before coding it. most of the work of an app isn't platform specific. There is may be just the threads...Input Output, networking and other things like that. 1 + 1 will always be 2 on every platform. a for loop will do the same thing on every platform. But reading a file may be a bit different. But not enough to say that it is hard. It may be just a bit annoying to do. But i like doing things like that. Oh and using VM doesn't mean absolutely cross platform. FlexBuilder 2...a plugin written in java for eclipse only available for Mac and windows. I would really like to know how they made non cross platform code using Java...
Auto package for happy pinguin ....
http://autopackage.org/
The fact is that installing from source is a really bad thing. Not that it don't work or it's difficult. But but having file spreaded everywhere is not a good thing. So then package is really great...
One of the thing that would be great is... having the source archive and open it with let say synaptic. then synaptic would find the needed dependencies so it should work and make the sources in a temp directory.
Then when it's done, synpatic do something like make install to install the file in a directory so he would be able to create a package for it. and install it cleanly. And finally putting every sources to trash except the archive.
Then you have something that in drag and drop would build/install a package from source
and having autopackage file for commercial binaries is a damn great idea. It's better than using the ugly .sh script....