Comment by 🕹️ skyjake

=> Re: "clagrange and resources.lgr location" | In: u/sy

The .config directory is not searched for resources.lgr, mostly because of the increased risk of getting a version mismatch. "resources.lgr" is usually strongly tied to a particular release of the app, so one must minimize the possibility of obsolete .lgrs hanging around and getting loaded by accident.

At one point I was embedding the .lgr inside the executable to make this foolproof, but that became unwieldly once there was 20+ MBs of fonts included.

Now the .lgr is back at ~4 MBs so I might again start embedding it, though.

clagrange needs no fonts or image assets, so embedding the resources is likely the best solution here. I'll just need to generate a TUI-specific subset of the .lgr for embedding.

=> 🕹️ skyjake [sysop]

2024-09-20 · 4 months ago

3 Later Comments ↓

=> 🚀 sy [OP] · Sep 29 at 13:00:

I've built v1.18.1 with -DCMAKE_BUILD_TYPE=Release -DENABLE_TUI=ON -DRESOURCES_LGR_PATH=/Applications/Lagrange.app/Contents/Resources to sync resources between builds. But clagrange adds the default bookmarks again for each run. I have ~/.config/lagrange/cprefs.cfg and ~/Library/Application Support/fi.skyjake.Lagrange/prefs.cfg files. Do I need another cmake flag pointing to to the config?

=> 🕹️ skyjake [...] · Sep 29 at 13:01:

I have actually seen that as well, the duplicated initial bookmarks, and it's a bug. I'll fix it for the next release...

=> 🕹️ skyjake [...] · Sep 29 at 13:13: | — The fix is in the dev branch now.

Original Post

=> 🚀 sy

clagrange and resources.lgr location — @skyjake What is the regular way to build/install clagrange? I've built it on macOS, but cannot use the binary if I copy it to PATH. The resource file is searched only in the binary's directory or some non-existing dirs. It works fine in the build dir, though. (And supports emojis better than Lagrange via terminal) Uncommenting the debug line in source, and running from ~/.local/bin/: [preformatted]

=> 💬 6 comments · 2024-09-20 · 4 months ago