FLTK logo

Re: [fltk.general] FLTK as an external dependency in Bazel?

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.general  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: FLTK as an external dependency in Bazel? Albrecht Schlosser Jan 29, 2023  
 
On 1/29/23 18:06 Zsolt Pajor-Gyulai wrote:

The problem was that a recent commit made fluid call Fl::add_fd() in a static initializer thread.
For some reason, Fl::add_fd() opens the display, specifically on macOS, not on other platforms.
Matt removed this early call to add_fd().
I find the problem of hanging build process to be fixed now.

Hopefully that also solves the OP's problem.

I might be too uninitiated, but what is the suggested solution? To use the dev version 1.4.0?

There are several suggestions. Everything we found out was about *building* FLTK in /tmp or a subdirectory of /tmp. If you didn't do this, it's probably not an issue, unless ...

In your previous post you wrote: "I found the compiled binaries and running it directly blocked the window as well."

Here are two questions:

(1) *where* did you find them, i.e. was this in or under /tmp?

(2) *how* did you "run the binaries directly"?

If these binaries are *not* inside /tmp then there's probably another problem, but *if* they are inside /tmp, read on:

First recommendation: check out the latest FLTK from git branch 'master' to get the latest fixes and build FLTK again.

Second recommendation: if Bazel can do it - or if you can do it yourself - create a macOS "bundle" and run the binaries from this bundle, for instance by `open my_prog.app`. You can also run a binary from within a bundle, for instance with `fluid` in the build directory 'fluid/fluid.app/Contents/MacOS/fluid'. This works for me, whereas 'fluid/fluid' would hang - although these binaries are really identical (checked with diff).

Third recommendation: copy the binaries to a place inside your home directory and run them from there.

Fourth recommendation: run the binaries with their *full* path, e.g. '/tmp/fltk/fluid/fluid'.

You can help us helping you and others if you try all recommendations and report whether each one works for you. Thanks in advance.

--
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/ef4a9ffc-3155-e1a9-a55e-7ca2d4c688b1%40online.de.
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.