Not the most interresting project in the world.. But for your leasure here is a short status update:
I have managed to build the bootstrapped version of CMake, and at the moment I am using it to build the real version of CMake for use with other projects. The bootstrapped version is only designed to be able to built cmake with itself.
The main problem was the kwsys/ProcessXXXX.c file that uses fork() and execve() and pipe() to call other processes. I have managed to do an implementation that uses IDOS->CreateNewProc() and my own amiga_pipe() for the purpose, but it is still in development and not necessarily complete.
I'd say give it another week, and I will release a beta.
Thanks y'all. I will consider boost-libs (I don't know anything about it at present), but I think my first commitment at the moment is to reap the benefits of the Qt bounty and actually create some apps for it. When all that is done, I might turn to other things.
@alfkil Make QT working fast and without visual bugs are very-very welcome :) I just stop to worry about it for now, as most of apps which i try to port was really slow :(
If you will need any help with it, i am open for testing as always.
@alfkill Yes finish QT first and then continue to boost-libs. Take a look at it and see if you think you can manage to port/update it. You always deliever
alfkil wrote: Thanks y'all. I will consider boost-libs (I don't know anything about it at present), but I think my first commitment at the moment is to reap the benefits of the Qt bounty and actually create some apps for it. When all that is done, I might turn to other things.
Before doing anything with Boost you should contact me.
kas1e wrote: @ssolie Btw, i read in your description over the old boost libs (from os4depot) that:
Quote:
thread - the SDK C++ compiler supports single threading only
Through, all the modern boost-related apps want that "libboostthread.a" , and so, maybe we can somehow still emulate it , if not just plainly port ?
IIRC, the problem is not running multiple threads itself, but what should happen when you use C++ features such as exceptions. For example, what should happen if an exception occurs in one thread, but needs to be handled in another? What mechanism should be used to handle such a case?
C++ can't stop you from starting new threads/tasks but, without C++ multi-threading support, you need to respect the limitations.
kas1e wrote: Through, all the modern boost-related apps want that "libboostthread.a" , and so, maybe we can somehow still emulate it , if not just plainly port ?
The sources for GCC are stored in adtools on sourceforge. If anyone is up to the challenge I certainly would really appreciate it. Note that if newlib is your C library there is a bug in GCC which causes C++ exceptions to fail so you'll need to fix that one first.
After the GCC work is done I could provide you with a Boost threading library in a few hours at most.
CMake is now 100% compiled (except the documentation). Of course it crashes when I try to run it, but still it should be "trivial" to fix it. The std::vector bug I mentioned in the other thread still spooks, but apparently it doesn't happen when I do not edit the CMakeLists.txt files.
I'm away from home for a couple of days, but when I get back I will upload asap. Cheers!
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
