Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
openmesh-python
openmesh-python
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenMesh
  • openmesh-pythonopenmesh-python
  • Merge Requests
  • !2

Merged
Created May 08, 2018 by Matthias Möller@moellerContributor

fix pythonpath by using generator expression

  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 1

With multi-configuration/crossplatform toolchains, the output path of a target varies from the selected configuration (most famous: Debug/Release on MSVC/xcode). Therefore, the module's output path is not the bin dir, but mostly in something like ${CMAKE_CURRENT_BINARY_DIR}/Debug or ${CMAKE_CURRENT_BINARY_DIR}/Release.

This MR fixes the path, so that pythonpath is always set to the correct path where the module was built into.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix-pythonpath