Hi,
What is the standpoint of the reactos project on using libraries, like for example wxwidgets for implementing reactos software (like reactos movie maker)?
Further is there any specification that says for example "everything has to be compilable with mingw", or "everything has to run on i386/pentium xx"?
Imre
What is the standpoint of the reactos project on using libraries, like for example wxwidgets for implementing reactos software (like reactos movie maker)?
This would just make the build process more complicated than neccessary, and increase compile time and download size (sources). Tools/Applications that come with ReactOS are not needed and expected to be ported to other architectures. We should stick to plain Win32/64 APIs. Also C is preferred over C++ a lot.
Further is there any specification that says for example "everything has to be compilable with mingw", or "everything has to run on i386/pentium xx"?
- No other tools/libraries neccessary on the host than the minimum build system (mingw, nasm, make) - Only use C++ when it makes sense, prefer C (not just because g++ is so extremely slow) - Don't include pre-built binaries in the repository, everything needs to be built from source code - Don't bloat the repository with tons of huge libraries (do we still have more than one xml library?!) - Software that is included in the base repository should not use frameworks for portability and use the APIs directly instead
That's my personal opinions and doesn't neccessarily match with those of the other developers.
- Thomas