mirror of
https://github.com/lucaspalomodevelop/meshlab.git
synced 2026-03-18 10:34:41 +00:00
The default shell context in NSIS is for the current user. This causes $SMPROGRAMS to put the link in the current user's profile. Other users on the system get no start menu link. This is causing me trouble because I'm trying to deploy Meshlab in a school and by default only the user that installs the application gets the Start Menu shortcuts. Docs for SetShellVarContext at https://nsis.sourceforge.io/Docs/Chapter4.htmL I also handled removing old currentuser shortcuts during uninstall/install.
Windows Scripts
WORK IN PROGRESS
This folder contains a series of scripts to build and deploy MeshLab under a Windows environment.
The follwing scripts are provided:
windows_build.ps1: this script compiles MeshLab in a Windows environment:- it requires a properly set Visual Studio (>=2015) and MSVC compiler;
- it requires a properly set Qt (>= 5.9) environment;
- without given arguments, all the binaries will be placed in the
meshlab/distribfolder. You can give as argument theBUILD_PATH, and meshlab binaries will be then placed insideBUILD_PATH/distrib;
windows_build_meshlab_mini.ps1: this script compiles MeshLab mini in a Windows environment. Works in the same way as thewindows_build.ps1script;windows_deploy.ps1: makes thedistribfolder a portable version of MeshLab (no Qt and other libraries dependencies):- it requires a properly built meshlab
distribdirectory (seewindows_build.ps1); windeployqt.exedirectly accessible by powershell andVCINSTALLDIRset to the VC Visual Studio;- without given arguments, the folder that will be deployed is
meshlab/distrib. You can give as argument theDISTRIB_PATH;
- it requires a properly built meshlab
windows_nsis_installer.ps1: this script generates an installer for MeshLab:- it requires a properly built and deployed meshlab
distribdirectory (seewindows_deploy.ps1); makensis.exedirectly accessible by powershell;- without given arguments, the folder used for creating the installer is
meshlab/distrib. You can give as argument theDISTRIB_PATH;
- it requires a properly built and deployed meshlab