Windows debug version

Version compiled in my computer

More or less functional LibreCAD3 Binaries

When executing the program, you may notice that the painter (screen where you draw the lines) is green. To solve this, press the top left option called "File" and click new. The new window will have a functional painter.

Appimage 18.04 with qt libraries

This Appimage has the qt plugins with linuxdeploy+linuxdeploy-plugin-qt. It works on the VM where it was built. Has a segmentation fault on my Laptop.

18.04 Ubuntu AppImage

I was able to execute this appImage and it kinda works i guess. Though it has a green screen and missing icons which I think also happens on the windows code.

AppImage 3rd try

I've packaged again the appImage but this time forcing it to package /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libstdc++.so.6. Hope it works now

Second try on Appimage

Using a different tool, Let's see if this one works correctly:

0.0.5 Windows

Solved Desktop shortcut problem, VC redistributables and automatic install of path.lua.

Everything should be smooth now ( There is still that problem with the icons not appearing on top, but I'll need confirmation that it happens in other computers).

0.0.4

AppImage Prototype, no idea if it works correctly. I can't upload Appimages so it's in the zip.

Alpha v003

a path.lua file is required to be created in the bin folder with the following content:

package.path = package.path .. ';../finalInstallDir/usr/share/librecad/lcUILua/?.lua'
ui_path='../finalInstallDir/usr/share/librecad/lcUI/ui'
plugin_path='../finalInstallDir/usr/share/librecad/lcUILua/plugins'
lua_path='../finalInstallDir/usr/share/librecad/lcUILua'

JSON settings are in bin, but application can't find default configuration.

v0.0.2

Made binaries be installed in bin instead of RelWithDebInfo and also filtered most useless files ( I have no idea where include folder is installed from ). Path.lua doasn't work, and is installed in C://bin instead of where it should be ( RootInstallFolder/bin).

This is a minor issue, I've managed to track where the include folder comes from. It seems it's from lckernel/tinyspline/src/CMakeLists.txt. The variable is TINYSPLINE_INSTALL_INCLUDE_DIR. It's used quite a bit, so i'll see if I can solve next patch.