<!-- @page { size: 21cm 29.7cm; margin: 2cm } P { margin-bottom: 0.21cm } -->
Hi Haiku users and developers
Im writting to You, because im feeling a little disturbed by path of development of haiku. As we all know the main target for haiku is BeOS compatibility. I was hoping that we will stay with gcc4hybrid, because its easier solution for developers wanting to dev / or porting apps to haiku. Unfortunately official Alpha 1 was released as gcc2hybrid. All ok, but what we have today? We're getting a lot of ports that uses additionally sdl gcc4 ports. This forces us to use both libs in haiku, and generates a really big mess in haikuOS builds [ some programs works / some not ]. We're getting into surreal situation that forcing us using both haiku builds - gcc2h and gcc4h to use some apps written for gcc4 and some for gcc2. I think we all need to find some substitute to this problem , otherwise we will not get anything more than messed shadow of real idea of haikuOS [ not to mention about lack of applications ]. haikuOS should be more user friendly than linux these days, this is our goal and we just cant bury the idea in this way..
Regards
Comments
They've mentioned that with R2, the API will change. This means gcc4 R1 programs will have to be re-compiled for R2 but gcc2 R1/BeOS programs should work with R2 without re-compiling (compatibility layer?) or they may drop gcc2 program support altogether in R2 (or R3).
The small price to pay to support BeOS gcc2 programs. Compiling should be done on gcc2hybrid system to stay compatible with released Haiku Alpha.
I believe Haiku Alpha includes gcc2 & gcc4 and can use setgcc to switch between the two.
I doubt. this games are written to fit with gcc3/gcc4, but I have no time to do this. Working for me and releasing to you is the best that I can do.
OpenJDK, Flash, Qt and Webkit requires work with gcc4. Haiku R2 will be all in gcc4 or gcc5.
Think in the future. If not, all the port will be revised to fit in R2 (avoiding the double work).
And I don't need work with Haiku gcc2 because goBe Productive (the app that maintains the Haiku binary focus) is useless today. I believe that Qt Office will fits better on Haiku
Not true.
Quoting michaelvoliveira:
gcc2 is the default compiler, whether you like it or not, which means most people are going to be using gcc2 based systems. All effort should be put into making software work with gcc2. gcc4 is only for emergency use when absolutely necessary.
gcc2 is the default compiler, whether you like it or not, which means most people are going to be using gcc2 based systems. All effort should be put into making software work with gcc2. gcc4 is only for emergency use when absolutely necessary.
Again... I have no time to do this. Working for me and releasing to you is the best that I can do.
Than you are not working for the community and should stop releasing the ports. It is fine that you can run the programs, but don't make a mess of haiku because you do not care to work within the community. Either use gcc2 and gcc2 libs or keep them to yourself. We don't need this mess.
cylindrix port
http://www.haikuware.com/directory/view-details/games/3d/cylindrix-haiku
and beastieworker port
http://www.haikuware.com/directory/view-details/games/3d/beastiewroler
all gcc2 all with my little effort to do an experimental OS usable
This will partally solve problem..
Of course i dont mind to have experimental apps on haikuware, BUT only if author will be trying to develop it into notexperimental stage [ for all ]
But if you compiling app / game and it works well only on your haiku..
my app / game don't work well only in my haiku machine
I do a clean build every week
install only my haikuware gcc 4 libs and the game that I want to play
fire and
works!
folks of #haiku-br do the same thing and works
+160 people that download fheroes2 in a whole month works
I don't have time is because I have only this vacation month to do that..
beyond that newer games needs of gcc >> 3 version to build. ported back to gcc2.95 is beyond my skills. I'm a lawyer.. not a computer scientist
RSS feed for comments to this post