LibreCAD - Re: dev environment setup and usage

Re: dev environment setup and usage

Posted by dxli on Feb 02, 2016; 11:33pm
URL: https://forum.librecad.org/dev-environment-setup-and-usage-tp5712883p5712884.html

Hi DErik,

please read through our wiki, even though updates are needed, like package names changed, executable paths changed, etc. The building process for LC is still by qmake.

also, read the building scripts come with LC in LC source folder:

scripts/build-osx.sh

DErik wrote

I thought I was. Refer to "https://github.com/thoughtbot/capybara-webkit/wiki/Installing-Qt-and-compiling-capybara-webkit" web page. I got there because I was trying to install Qt because the install instructions on "http://wiki.librecad.org/index.php/LibreCAD_Installation_from_Source" for building from downloaded source said to install Qt and new gcc. So after installing Macports (needed to install Qt), the installation for Qt using Macports says to: 
sudo port install qt5 # It's not qt5-mac anymore. 
That worked, so the next part of the instructions then say: 

The default location for qt5's qmake is /opt/local/libexec/qt5/bin/qmake. If the qmake on path is different, you can indicate the correct one with QMAKE environment variable. 

QMAKE=/opt/local/libexec/qt5/bin/qmake gem install capybara-webkit 

So that's why I did it. Qt appears to be installed and functional. But none of the examples are there to learn how to use it, nor are the help or man pages. The on-line manual pages will take some time to browse through for specifics on how to use Qt.

However, I did load the ~/github/LibreCAD/librecad.pro file into Qt and am able to browse through the source files and even bring up the GUIs. So I can now do some of the research I need to do even if the installation isn't quite correct or complete. I should also mention that I attempted to run a debug session via Qt, but it didn't compile. I got over 58000 issues listed; and it quit outputting to the "Compile Output" window. (I guess it knew I wasn't going to read through all that stuff anyway.) I figure it is still due to an incorrect or incomplete download or installation of Qt or Macports or some other setup I didn't do correctly. Recall that **qmake** is actually on my system now, but I have to manually add it to my PATH variable in a console window. It isn't part of my automatic startup script for the console (.bashrc). I guess I'll have to create that file and add a PATH modification to it for the qmake directory. But Qt should know where all its stuff is already.