Skip to content

Conversation

@exilief
Copy link
Contributor

@exilief exilief commented Jul 7, 2025

This adds a photodiode example that utilizes my FDTD library for postprocessing, so it must be decided how it should be linked. You may decide to also make a fork of my library for maintenance.

To ensure a correct version is used, should the build system include it as an optional dependency, or does the user have to manually install it and make it available? Is there an example where such a case is already handled?
A similar issue is present for the Eigen library used in the ViennaCS diffusion example, see the PR.

@exilief exilief force-pushed the photodiode-example branch from 1f614ed to 7034315 Compare July 27, 2025 18:30
@exilief
Copy link
Contributor Author

exilief commented Jul 27, 2025

I now added basic CMake support to my library. The user must manually download and install it and add it to CMake's search paths when building ViennaPS with examples. It should then be found by find_package(), or print a message if missing, like for Eigen in ViennaCS (diffusionImplicit example).
I only tested it on Linux.

@exilief exilief marked this pull request as ready for review July 27, 2025 18:39
@exilief exilief force-pushed the photodiode-example branch from 7034315 to 84385fd Compare August 4, 2025 12:50
@tobre1 tobre1 merged commit 341ee28 into ViennaTools:master Aug 4, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants