# rc2: InnoSetup: relative filenames not interpreted as relative to CMAKE\_CURRENT\_SOURCE\_DIR
**URL:** https://discourse.cmake.org/t/rc2-innosetup-relative-filenames-not-interpreted-as-relative-to-cmake-current-source-dir/8381
**Category:** Development
**Created:** [June 21, 2023, 8:58pm UTC](https://discourse.cmake.org/t/rc2-innosetup-relative-filenames-not-interpreted-as-relative-to-cmake-current-source-dir/8381 "2023-06-21T20:58:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@neundorf](https://discourse.cmake.org/u/neundorf)
#### Post date: [June 21, 2023, 8:58pm UTC](https://discourse.cmake.org/t/rc2-innosetup-relative-filenames-not-interpreted-as-relative-to-cmake-current-source-dir/8381/1 "2023-06-21T20:58:10Z")
Hi,
I’m giving the new innosetup generator a try.
Good news, it works 🙂
I noticed that CPACK\_PACKAGE\_ICON and CPACK\_RESOURCE\_LICENSE\_FILE don’t interpret relative paths as relative to CMAKE\_CURRENT\_SOURCE\_DIR.
I.e.
set(CPACK\_PACKAGE\_ICON my.bmp)
is not enough, I have to do
set(CPACK\_PACKAGE\_ICON “${CMAKE\_CURRENT\_SOURCE\_DIR}/my.bmp”)
the same for CPACK\_RESOURCE\_LICENSE\_FILE.
Is this expected behaviour or a bug ?
---
### Author:  [@craig.scott](https://discourse.cmake.org/u/craig.scott)
#### Post date: [June 21, 2023, 10:14pm UTC](https://discourse.cmake.org/t/rc2-innosetup-relative-filenames-not-interpreted-as-relative-to-cmake-current-source-dir/8381/2 "2023-06-21T22:14:13Z")
I assume you meant `CPACK_RESOURCE_FILE_LICENSE`. That should always be specified as an absolute path. I don’t have specific notes for `CPACK_PACKAGE_ICON`, but I would assume it too should be an absolute path. I would assume this needs to be the case because the variables are simply passed through to `cpack`, they are not used directly during CMake’s configure step. By the time `cpack` runs, it has no concept of `CMAKE_CURRENT_SOURCE_DIR`.