fierst / parts-db-editor

Database front-end tool for an Altium .DBLib, with an emphasis on manufacturer information
3 stars 1 forks source link

how to compile #7

Open ddavidebor opened 6 years ago

ddavidebor commented 6 years ago

Hi, do you have istructions to compile?

fierst commented 6 years ago

Other than what's included in the repository, you will need to have a copy of the boost libraries on your local machine. boost::filesystem is used throughout the parts-db-editor project for filesystem parsing and directory traversal, which requires the pre-compiled boost_filesystem and boost_system libraries. These are pretty easy to build with the b2 tool included with the boost libraries.

It's been a while since I've looked at this code as I'm no longer using Altium Designer on a daily basis, but I was able to successfully build the project on a different machine after taking care of the boost dependency.

Sildeon commented 6 years ago

I have tried to compile, but I unfortunately am unfamiliar with the boost libraries. I have compiled them multiple times, but am still unable to get the part-db-editor to compile in QT due to missing dependencies from boost.

Any help would be greatly appreciated.

fierst commented 6 years ago

If you've built the static boost libraries, then you'll need to update the .pro file within the QT project to point to the proper location and libraries.

At the top are two lines, INCLUDEPATH and LIBS:

Make sure that INCLUDEPATH points to the directory where your boost folder is. You can verify that this is correct by right clicking on one of the boost includes and attempting to open it. If it can be opened, then you've got the right path.

Make sure that LIBS points to the directory where you built the static boost libraries and that the filenames (prepended by '-l') match the boost libraries you've built. In my case, they were libboost_[library_name]-mgw53-mt-d-x32-1_67 but that filename is heavily dependent on which compiler you've used, whether you've got debug support enabled, what version of boost you have, etc. If you look in the directory where you've built the boost libraries, you should see how to format those strings.