Tasks #1443

Check pkg-config

Added by Anonymous about 11 years ago. Updated almost 11 years ago.

Status:ResolvedStart date:02/27/2013
Priority:NormalDue date:
Assignee:S. Wrede% Done:

100%

Category:-Estimated time:1.00 hour
Target version:Robotics Service Bus - rsb-0.9

Description

Continuously check pkg-config on the CI server


Related issues

Related to Robot Control Interface - Tasks #1486: Check pkgconfig Closed 05/06/2013

Associated revisions

Revision c02111db
Added by Arne Nordmann about 11 years ago

Test script for checking pkg-config

  • Builds simple main file with a subset of rsc sumbols, using pkg-config for configuration

refs #1443

Revision cb9af899
Added by Arne Nordmann about 11 years ago

Pkg-config test now integrated into ctest

  • pkg-config test now installs project first to a tmp folder
  • Adapts prefix in installed pkg-config file and sets PKG_CONFIG_PATH
  • pkg-config test added as ctest, so separate CI job for pkg-config testing can be deleted

fixes #1443

Revision 63de2bd0
Added by Arne Nordmann almost 11 years ago

Fixed include path for 3rdpart boost uuid export in pkgconfig file

  • Fixed include path for 3rdpart boost uuid when shipped together with rsc
  • generate JUnit XML result for pkgconfig test to be processable by our CI setup

refs #1443
refs #1504

Revision c52c500e
Added by J. Wienke almost 11 years ago

Do not assume a certain build layout for the pkg-config test.

refs #1443

Revision ea0b9b96
Added by Arne Nordmann almost 11 years ago

Fixes pkgconfig test for Mac

  • On Mac the command 'mktemp' expects a template for the tmpdir name to create. Added this to the pkgconfig test script, since this is a legal (yet optional) parameter on linux.

refs #1443

History

#1 Updated by Anonymous about 11 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#2 Updated by J. Moringen about 11 years ago

  • Status changed from Resolved to Feedback

Couldn't the whole test associated with this test script be integrated via ctest?

Then, make test would just include the new test.

#3 Updated by Anonymous about 11 years ago

  • % Done changed from 100 to 50

This means, that the test will have to install the package first, but this should be possible. I will try to do this.

#4 Updated by Anonymous about 11 years ago

  • Status changed from Feedback to In Progress

#5 Updated by Anonymous about 11 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Applied in changeset rsc|commit:cb9af899acf1b410479c8015d5b58c9ba2ae848e.

#6 Updated by S. Wrede almost 11 years ago

  • Status changed from Resolved to In Progress
  • Assignee deleted (Anonymous)
  • % Done changed from 100 to 50

We probably need a MacOS test for this and a switch in the CMake File that writes the complete library name in the rsc.pc.in file as the library name formatting on MacOS seems to follow a different layout as shown in these examples:

kt  2012 libsigc-2.0.0.dylib -> ../Cellar/libsigc++/2.2.10/lib/libsigc-2.0.0.dylib
lrwxr-xr-x    1 swrede  admin    48B  2 Okt  2012 libsigc-2.0.dylib -> ../Cellar/libsigc++/2.2.10/lib/libsigc-2.0.dylib
-rw-r--r--    1 swrede  admin   186K 16 Nov 23:30 libskinDynLib.a
lrwxr-xr-x    1 swrede  admin    47B  5 Jun  2012 libslang.2.2.4.dylib -> ../Cellar/s-lang/2.2.4/lib/libslang.2.2.4.dylib
lrwxr-xr-x    1 swrede  admin    43B  5 Jun  2012 libslang.2.dylib -> ../Cellar/s-lang/2.2.4/lib/libslang.2.dylib
lrwxr-xr-x    1 swrede  admin    41B  5 Jun  2012 libslang.dylib -> ../Cellar/s-lang/2.2.4/lib/libslang.dylib
lrwxr-xr-x    1 swrede  admin    48B  8 Nov 17:06 libsoup-2.4.1.dylib -> ../Cellar/libsoup/2.38.1/lib/libsoup-2.4.1.dylib
lrwxr-xr-x    1 swrede  admin    42B  8 Nov 17:06 libsoup-2.4.a -> ../Cellar/libsoup/2.38.1/lib/libsoup-2.4.a

The same logic should be added to the other projects where we offer pc-files.

#7 Updated by J. Moringen almost 11 years ago

I think this issue is about automatically testing the generated pkg-config files.

#8 Updated by J. Moringen almost 11 years ago

Again: Wasn't this supposed to add a test which ensures that generated pkg-config files work? If so, can we close this issue and open new issues for additional tests?

#9 Updated by Anonymous almost 11 years ago

  • Status changed from In Progress to Resolved
  • Assignee set to S. Wrede
  • % Done changed from 50 to 100

Test was added and automatically tests pkgconfig on UNIX systems.

@Sebastian: The test also runs on the MacOS machine, it was just not evaluated by the CI job until some minutes ago. However, since #1498 is resolved, pkgconfig should now be the same for MacOS and Linux now. Can you file an issue, if this is not the case?

Also available in: Atom PDF