|
|
Thank you all, this did the trick for me too!
To close out, I wanted to commemorate how I ended up using FLTK with
bazel as it was some trial and error. Just in case it's useful for
someone else too.
1. Clone FLTK from repo
2. Build with ./configure and make.
3. Add BUILD file in fltk checkout with content:
```
cc_library(
name = "fltk",
hdrs = glob(["FL/*.h", "FL/*.H"]),
srcs = glob(["lib/*.a"]),
includes = ["."],
linkopts = ["-Lfltk/lib", "-lfltk_forms", "-lfltk_gl", "-lfltk",
"-lfltk_images", "-lfltk_jpeg", "-lfltk_png", "-lfltk_z", "-lm",
"-ldl", "-lpthread", "-framework Cocoa"],
visibility = ["//visibility:public"],
)
```
4. reference it as `//path/to/fltk:fltk`.
There is probably a more elegant way, but it works.
Thanks again!
On Mon, Jan 30, 2023 at 7:18 PM Manolo <manolo.gouy@gmail.com> wrote:
>
>
>
> Le lundi 30 janvier 2023 à 20:45:30 UTC+1, Greg a écrit :
>
> On 1/30/23 11:16, Manolo wrote:
>
> Problems to launch unbundled macOS apps from /tmp should be fixed with commit 1045538
>
> Oh wow, I didn't know unbundled macOS apps could work at all.
>
> Back in ye olde days running an unbundled app (just the executable, no .app directory)
> did all kinds of weird window behavior things.
>
> So that "works" now? Sounds great if so.
> I always thought that was kinda weird when it didn't work just because it couldn't
> find those minimal plist files.
>
> ===== reply ====
> FLTK supports unbundled macOS apps. SInce macOS 10.13 (2017), FLTK needs to start
> the event loop of unbundled apps differently than what it does for bundled ones:
> [NSApp finishLaunching];
> vs
> [NSApp run];
> This requires that FLTK detects at run time whether a bundled or unbundled app
> is being started.That is done comparing two folder paths, and when the unbundled app
> is /tmp/fltk/prog, the comparison became "/tmp/fltk" vs "/private/tmp/fltk" which
> were detected as different although they actually refer to the same folder. Then,
> the event loop starting means adequate for bundled apps was used, and blocked the app.
> This is now fixed.
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "fltk.general" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/fltkgeneral/miGhgA3y0xE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to fltkgeneral+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/8dea607a-387d-4e83-86b5-b521c0886e22n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/CADaF38TiegJjFv6pwBgnHhAHCEedFtN6_gV0b8B7szAvj_HWAQ%40mail.gmail.com.
[ Direct Link to Message ] | |
|
| |