Re: Documentation for LibreCAD Developers
Posted by Shawn.Curry on May 25, 2019; 6:58am
URL: https://forum.librecad.org/Documentation-for-LibreCAD-Developers-tp5717390p5717404.html
Fair enough, I suppose we can "agree to disagree" on the Visual Studio point (c'mon man, it's the appendix!) as long as it's linked to from the main area. Will you accept any of my other critiques of the windows process? I feel like this really hasn't been tested from scratch lately. Now that everything is working again you should try uninstalling everything and starting over.
1. The Qt offline installer path should not be recommended. They no longer offer this method from the main page; these installers can now only be found deep in their archive. My coworker, Doug, who follows instructions with superhuman precision, tracked these down and got into a real mess because of it.
They don't include the "kits" (libraries + compiler) that you need. These need to be located, downloaded, installed, and configured separately with much effort if you take this path. Your steps don't mention this part. The online installer allows you to not only install the program but also select the latest versions every available kit you might want. Plus, this path makes it possible to use the windows "Add/Remove Programs" dialog to reconfigure your kits later on. Otherwise you can't. Had to figure this all out the hard way.
If you're building with Qt, choose from the MinGW kits (32 or 64bit). If you want to build with Visual Studio, choose from the MSVC kits. Or both if you like.
2. If you want to save some space, there's really no reason to mention muParser. Its simply an included library, there's no way you could do anything different with the way the project is set up. I mean you could, but the process would certainly be more involved than the Visual Studio build.
3. Tell ya what. Include my VS steps, and I'll pay for it by eliminating the file copying steps. I can make a batch file to run the windeployqt.exe tool, which is the proper way to deploy the files anyway (it scans all current dependencies, you'll get the translation languages, etc). Then you can just tell folks to run that.
URL: https://forum.librecad.org/Documentation-for-LibreCAD-Developers-tp5717390p5717404.html
Fair enough, I suppose we can "agree to disagree" on the Visual Studio point (c'mon man, it's the appendix!) as long as it's linked to from the main area. Will you accept any of my other critiques of the windows process? I feel like this really hasn't been tested from scratch lately. Now that everything is working again you should try uninstalling everything and starting over.
1. The Qt offline installer path should not be recommended. They no longer offer this method from the main page; these installers can now only be found deep in their archive. My coworker, Doug, who follows instructions with superhuman precision, tracked these down and got into a real mess because of it.
They don't include the "kits" (libraries + compiler) that you need. These need to be located, downloaded, installed, and configured separately with much effort if you take this path. Your steps don't mention this part. The online installer allows you to not only install the program but also select the latest versions every available kit you might want. Plus, this path makes it possible to use the windows "Add/Remove Programs" dialog to reconfigure your kits later on. Otherwise you can't. Had to figure this all out the hard way.
If you're building with Qt, choose from the MinGW kits (32 or 64bit). If you want to build with Visual Studio, choose from the MSVC kits. Or both if you like.
2. If you want to save some space, there's really no reason to mention muParser. Its simply an included library, there's no way you could do anything different with the way the project is set up. I mean you could, but the process would certainly be more involved than the Visual Studio build.
3. Tell ya what. Include my VS steps, and I'll pay for it by eliminating the file copying steps. I can make a batch file to run the windeployqt.exe tool, which is the proper way to deploy the files anyway (it scans all current dependencies, you'll get the translation languages, etc). Then you can just tell folks to run that.
| Free forum by Nabble | Edit this page |