C:\Qt\Qt5.4.0\5.4\mingw491_32 is the default path from Qt installer for Windows.
When the path was changed during setup or a newer Qt release, e.g. 5.4.1 is used, you have to set up a costum.nsh in LibreCAD's scripts\postprocess-windows folder, as described in the wiki
And please check the custom-windows.bat paragraph too, this needs to be adjusted too, when the Qt location differs from standard.
The custom* files are to support multiple development platforms. Not only different OS are handled with them, even on Windows different Qt versions are used by individuals.
With the custom* files each developer can adopt the build process to his environment without affecting the git version control.
I spent most of yesterday updating the article you are referring me to.
That is my* costum.nsh ;-]
I was pointing out that:
C:\Qt\Qt5.4.0\5.4\mingw491_32 is NOT the default path for Windows.
The folder "Qt5.4.0" is erroneous... I did not customize my install.
*Actually I notice you changed the QT_Dir from "C:\Qt\5.4" to "C:\Qt".
Honestly, I'm not sure this line even does anything,
because it originally pointed to a folder that doesn't exist "Qt5.4.0" , and yet the build worked.
There is also the fact that in my second build the folder "Qt5.4.0" did not exist in my custom.nsh,
yet it still appears in the warning; and the build still worked.
My conclusion is that line 97 of nsis-5.4.nsi might be the problem:
The build worked with no warnings while my file had
Is it supposed to be
Also, I have noticed that when using git to update the source it complains of unstaged changes,
and refers to custom.pro
Using 'git stash' works; however, I thought custom.pro was supposed to be ignored.
What I can say now from memory is:
For me the unchanged Qt installation folder was C:\Qt\5.4.1\5.4.
And since nsis-5.2.nsi we use this notation for Qt location.
Iirc I had a similar case when I changed from 4.8 to 5.2, my installation differs from the project settings too.
The C:\Qt\MAINTENANCE_VERSION\RELEASE_VERSION makes sense when one have to use multiple versions concurrent.
I will also check your wiki changes tomorrow, the wiki should be consistent with the settings in the latest git managed files.
Maybe, that the QT_DIR setting in custom-windows.bat is obsolete, since we use windeployqt to grab Qt libraries for the installer package. Will check this tomorrow too.
Concerning unstaged changes, you're right, custom.pro should be ignored by .gitignore file in the LibreCAD root folder. My first thought was about capital letters in the filename (for git this matters on Windows), but then the git message should be unversioned files.
Unstaged changes means, that custom.pro is part of the git repo, maybe it was added by accident.
you undo changes and files are reset to the last clean state.
You may want to unstash your changes with
git stash pop
and then try to delete custom.pro from the index with
Hello people LibreCAD have a question.
Is there any option to create a line with a measure but without using the "@".
I give an example: create a point and then mark as example 2 but without using coordinates or use @.
Hola gente de librecad tengo una pregunta.
Hay alguna opción de crear una línea con una medida pero sin usar el "@".
Quiero dar un ejemplo: crear un punto y luego marcar la medida ejemplo 2 mm pero sin usar coordenadas ni usar @.