Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #21

Closed
Open
Created Jan 26, 2017 by snuverink_j@snuverink_jDeveloper

Build system puts Boost include directory before OPAL include directories

The build system puts the Boost include directory before the OPAL include directories. When installing OPAL in the same directory as where boost resides (I know perhaps not the best idea), a new build will give preference to the header files in the install directory. This gives compilation errors when the files are updated.

I was able to fix this by putting the OPAL include directories explicitly before others (see attached patch).

Assignee
Assign to
OPAL 1.5.1
Milestone
OPAL 1.5.1
Assign milestone
Time tracking