Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • CMake CMake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,806
    • Issues 3,806
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMake
  • CMakeCMake
  • Issues
  • #16993

Closed
Open
Created Jun 19, 2017 by Robert Maynard@robertmaynardDeveloper

CUDA: Visual Studio integration bugs prior to 8.0.61

When building shared libraries using Visual Studio the CUDA msbuild section are missing the <target_name>_EXPORTS define.

This looks to be caused by cmVisualStudio10TargetGenerator not storing ``target->GetExportMacro()` as a define for the CUDA language.

Discussed on mailing list:

  • June 2017: Missing <target>_EXPORTS definition in CUDA host compilation
Edited Jun 20, 2017 by Brad King
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking