Changes between Version 4 and Version 5 of FDORfc21
- Timestamp:
- 05/23/08 04:05:21 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc21
v4 v5 1 = FDO RFC 21 - New Linux Buildsystem C make Based =1 = FDO RFC 21 - New Linux Buildsystem CMake Based = 2 2 3 3 This page contains a request for comments document (RFC) for the FDO Open Source project. … … 29 29 * Is still be possible to have a ThirdParty directory as a convenience and/or make recomendation about which is the prefered/recommended versions by FDO team. Providing a thirdparty dir indeed relieve the user of need to discover what is happening, but you are narrowing the possibility of deploying this widespread. Is quite common as an example the distro have one only db devel version, and forcing user to choose a different one and add on your system without any update/security updates garanteed is complicated. For an shor answer to '''a)''', provides a link to the version recomended on documentation and a build script for everything and for '''b)''' quite the same, except that now we would be able to create a database of results, not stucked on old somtimes not so safe code, even been working. 30 30 31 The whole motivation behind the change is make FDO not touch any kind of internal thirdparty sources, using only provided distribution libraries, and make it easy to compile and work with core or providers separated. CMakeis one of the frameworks that allow us to do this.31 The whole motivation behind the change is make FDO not touch any kind of internal thirdparty sources, using only provided distribution libraries, and make it easy to compile and work with core or providers separated. [http://www.cmake.org/ CMake] (Cross-Platform Make) is one of the frameworks that allow us to do this. 32 32 33 33 With this, the possibilities of improvement are huge, as will become easy to deal with debugging/analysing independent parts of code, without rely on restart whole bs scripting.