Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #545

Closed
Open
Created Aug 09, 2016 by James Willenbring@jmwilleOwner

PyTrilinos library being exported when it shouldn't be

Created by: bmpersc

Bill Spotz reported that the export system for Trilinos is exporting the PyTrilinos library which is a problem since it depends on the python library. This causes linking errors when people use find_package(Trilinos) to get all the necessary information for Trilinos. The PyTrilinos library is in the list of Trilinos libraries, but it won't ever link. The sticking point here is that this library needs to be installed to work properly, but should not be in the export files.

I'm not sure of the right way to solve this. Should this be a special option passed in to the tribits_add_library? would doing that have impact on linking other things that are currently working? Maybe this should be a post processing step stripping it out for only the export. We'll need to look into the right way to do this.

Assignee
Assign to
Time tracking