Tip: its a good practice to backup your older files
- Download latest Fuselibs and Uno:
2.1. Get the prerequisites (Mono, Make, NodeJS and NuGet via mono)
make releasefrom terminal/command line of the Uno folder
2.1. Get the prerequisites (Mono, Bash via MSYS2, NodeJS and NuGet)
2.1.1. Get all the 64bit versions!
2.1.2. Bash - don’t forget to install and update the packages by running
pacman -Syuinside MSYS2, close the app, then run
pacman -Suto update the rest of the packages.
2.1.3. Bash - Add path to your environment variables “C:\msys64\usr\bin” and “C:\msys64\usr\local\bin” via Control Panel > System > View advanced system settings > Environment Variables > System Variables > Path (Ref)
2.1.4. Mono - Add path to your environment variables “C:\Program Files\Mono\bin”
2.2. Get Visual Studio (Select “.Net desktop development” if installing via VS Community 2017)
uno.slnin the uno-master folder
2.4. In VS, make sure “Uno.CLI.Main” is selected in Startup Projects dropdown, then click Start
2.5. Run the uno in the /bin folder
2.6. Side thought: I don’t think we need bash and nodejs for Windows VS route, perhaps someone can confirm this?
Setup latest Fuselibs with your project
3.1. Create a file named
.unoconfigin your project folder
3.2. Enter the path to the fuselibs in the file on the first line like so:
Packages.SourcePaths += /github/fuselibs/Source
Setup latest Uno
You will find your compiled Uno in the release folder
4.1. Copy uno executables(uno & uno.exe) to fuselibs/Stuff folder
4.2. Copy lib folder to fuselibs/Stuff/lib folder
4.3. Mac: Copy and rename the bin folder to Uno folder in the Fuse application:
Win: Copy contents of bin folder into
Program Files (x86)/Fuse
uno doctorin project folder to make sure your libs are up-to-date.
Run or export as per usual
P.s. if I’ve left anything out, just let me know.