On 2017/01/09 10:31, Karel Gardas wrote:
> Passing -llibobs.so.0 to linker means that linker will try to link
> liblibobps.so.0.so IMHO. Please give a try to -lobs
You can't modify what cmake passes to the linker in such a direct manner.
Jordon wrote:
> > Part 2: Leaning that OpenBSD does not have a wrapper for sys info.h. In
> > digging into this, I found that it is only used to get the amount of
> > physical RAM to dump to a log. That’s it. I just commented it out for now
> > with an intent to come back later and figure out the OpenBSD way to do this.
I think the figure they're after is sysctl hw.physmem. I agree with your
approach here.
> > Also, when I got the error, I noticed that if I immediately did
> > a ‘make build’ again, it would build a few more (as in, in the [x/y]
> > counter, the y would be a bit smaller). Doing this over and over would
> > slowly decrement the number of remaining files to a point at which it
> > stopped decrementing. This makes the build seem… nondeterministic? Is
> > this just a function of a parallel build system that stops whenever it
> > sees an error?
Builds done using ninja (which is default for cmake ports) are non-
deterministic. (It's sort-of useful during development, but a complete
pain as far as bulk builds are concerned, and makes it hard to find
differences between working and non-working builds). Anyway don't
worry about this for now, it's not going to have much effect on this
port.
> > /usr/bin/ld: cannot find -llibobs.so.0
Set SHARED_LIBS=obs 0.0, clean and rebuild.
While you're there, you might as well also set the others and save
yourself some extra rebuilds -
SHARED_LIBS= obs 0.0 \
obs-frontend-api 0.0 \
obs-opengl 0.0 \
obsglad 0.0
BTW if you want to submit this, make sure it gets a build on a -current
machine with up-to-date packages and ports tree; Qt5 has been reorgnasied
recently and Qt5X11Extras moved from the main Qt5 package to
x11/qt5/qt5extras.
I suggest skipping the v4l2 plugin for now, webcam input is available
via an ffmpeg source of /dev/video0 (format "video4linux2") anyway,
and that one will be tricky.
> > So the ‘cannon find’ file is right where it should be. Can any of
> > you experienced porters see what rookie mistake I am making?
It's not a rookie mistake, you hit a fiddly area of the cmake ports
infrastructure. Some parts of the build require that the generated
libraries are defined in SHARED_LIBS, however you don't know what they
are until you've attempted build. (Sometimes it fails during build,
sometimes it "succeeds" but doesn't install things correctly).
