Administrator
|
@All,
I came to a decent point changing the build order and I am happy with the result so far, unfortunately I wasn't be able to complete it yet and there is more work comming. For instance settings.pro needs to get populate with settings still, and these include location of boost library, various names and compiler flags. The idea is that downstream package builders only have to touch/patch the settings file to make it suitable for there environment. The build also is changed so that each library/tool/program will have it's own intermediate directory where object/ui and what not files are stored. However, this directory was renamed to 'generated' to make it clear that in there is generated content. package builders (or we) can then make a simpel clear script and search for these generated directories. Main reason why I couldn't continue was because now that LibreCAD depends on c++11,I need to download a install new compilers (I have gcc 4.2 apparently) and I need to update this to 4.4 or 4.6. This also means that daily builds are broken at the moment! Ries On Feb 15, 2012, at 4:01 PM, ClaudeQC [via LibreCAD] wrote:
|
Hello Ries, On 15/02/2012 21:51, R. van Twisk [via LibreCAD] wrote: > > Main reason why I couldn't continue was because now that LibreCAD depends > on c++11,I need to download a install new compilers (I have gcc 4.2 > apparently) > and I need to update this to 4.4 or 4.6. > - Interesting. - Will all people wanting to built LibreCAD will have to do such an update to GCC ? - Is the price (all built problems) for being able to use C++11 is a little bit too high ? Claude |
Administrator
|
On Feb 16, 2012, at 11:52 AM, ClaudeQC [via LibreCAD] wrote:
No, this should only count for OSX user who are still on gcc 4.2 Any OSX user I will personally help getting up-and-running.
As far as I can tell, we should be fine on Windows where the Qt SDK comes with gcc 4.4 However, I don't want separate gcc installations on windows because tat opens a whole new set of problems like re-compiling Qt, that's what we need to prevent. On Windows it should only need a Qt SDK + Qt Creators (comes in a package) and unzipping boost into a directory. I am working to make this more clear and give better warnings during the qmake process. How I started LibreCAD (and CADuntu at the time) I re-organise the build method so it was just about running qmake and make. Because of this it was/is very easy to build on various operating systems, and before each commit I would even test it on Linux, OSX and Windows. This to ensure I would gain more developers. The old QCad build was crap…. So, my goal for this reorganization is to keep the builds KISS for Windows and Linux, but I am ok for OSX if it needs a different compiler then what comes with OSX because on OSX there is ports that has gcc 4.4, 4.5 and 4.6, to make it fairly easy. Boost is unfortunately needed but I am thinking to use https://github.com/ryppl/boost-svn/tree/Boost_1_48_0 so a user can checkout LibreCAD with git in one command. If a user doesn't have git, then it is properly going to be as simple as downloading boost and unzip it into a directory. Ries
|
Free forum by Nabble | Edit this page |