Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RelWithDebInfo build does not copy pdb files into install folder with Visual Studio #5577

Open
1 task done
owillebo opened this issue Jan 15, 2025 · 0 comments
Open
1 task done
Labels
triage Issue pending classification

Comments

@owillebo
Copy link

owillebo commented Jan 15, 2025

Is there an already existing issue for this?

  • I have searched the existing issues

Expected behavior

The CMake RelWithDebInfo build target is for building a Release build with debug information. With Visual Studio, debug information is stored in separate pdb files.

The build deliverables including the pdb files must be stored in to the install\XXXX folder (XXXX is the target, i.e. fastdds,fastcdr,...).

Current behavior

For Debug builds these pdb files are copied in to the install\XXXX\lib folder.

For RelWithDebInfo builds pdb files are generated but NOT copied in to the install\XXXX\lib folder.

Steps to reproduce

Just build with RelWithDebInfo.

colcon build --cmake-args " -DCMAKE_BUILD_TYPE=RelWithDebInfo" --packages-up-to fastdds

No pdb files are generated in the install\XXXX\lib folder.

The pdb files are generated in the build\XXXX\src\cpp\RelWithDebInfo folder.

Fast DDS version/commit

repositories:
    foonathan_memory_vendor:
        type: git
        url: https://github.com/eProsima/foonathan_memory_vendor.git
        version: v1.3.1
    fastcdr:
        type: git
        url: https://github.com/eProsima/Fast-CDR.git
        version: v2.2.6
    fastdds:
        type: git
        url: https://github.com/eProsima/Fast-DDS.git
        version: v3.1.1
    fastddsgen:
        type: git
        url: https://github.com/eProsima/Fast-DDS-Gen.git
        version: v4.0.3

Platform/Architecture

Windows 10 Visual Studio 2019

Transport layer

Default configuration, UDPv4 & SHM

Additional context

No response

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

@owillebo owillebo added the triage Issue pending classification label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue pending classification
Projects
None yet
Development

No branches or pull requests

1 participant