Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#12595 closed bug (fixed)

Create a symlink to the cppunit library

Reported by: Max-Might Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Build System Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

To run the unittests application we need libcppunit.so It is built in another directory so we need to create a symlink or copy the library to the unittests lib directory. This patch creates a symlink to libcppunit.so

Attachments (1)

0001-unittests-link-libcppunit.so-to-the-unittests-direct.patch (872 bytes ) - added by Max-Might 9 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Max-Might, 9 years ago

patch: 01

comment:2 by bonefish, 9 years ago

I'd probably just build the library with UnitTestLib instead.

comment:3 by Max-Might, 9 years ago

But UnitTestsLib adds a dependency to libcppunit.so and it confuses jam.

https://github.com/haiku/haiku/blob/master/build/jam/TestsRules#L37

comment:4 by pulkomandy, 9 years ago

Resolution: fixed
Status: newclosed

Applied in hrev 50040.

in reply to:  3 comment:5 by bonefish, 9 years ago

Replying to Max-Might:

But UnitTestsLib adds a dependency to libcppunit.so and it confuses jam.

Good point, I missed that. Symlinks have the problem that they never are never updated and thus e.g. ignorant to DEBUG level changes. I usually prefer explicit installing when preparing "execution environments" (e.g. http://cgit.haiku-os.org/haiku/tree/src/tests/Jamfile?id=bb0ca427dfb92ec6c7cf93389e05e3b4d8a050e8#n19) -- this also provides convenient pseudo targets that just build an prepare everything. Not sure why the unit test stuff works differently. Possibly it's just very old and didn't receive much consideration when the build system was restructured later on.

Note: See TracTickets for help on using tickets.