We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Problem seems to be the STATIC objects we use. If you link the resource directly to the executable
modified core/src/filed/CMakeLists.txt @@ -60,11 +60,6 @@ if(HAVE_WIN32) ) endif() -if(HAVE_WIN32) - bareos_configure_file(FILES ../win32/filed/filedres.rc.in) - list(APPEND FDSRCS ${CMAKE_CURRENT_BINARY_DIR}/../win32/filed/filedres.rc) -endif() - include_directories(${OPENSSL_INCLUDE_DIR}) add_library(fd_objects STATIC ${FDSRCS}) @@ -76,6 +71,11 @@ endif() add_executable(bareos-fd filed.cc) +if(HAVE_WIN32) + bareos_configure_file(FILES ../win32/filed/filedres.rc.in) + target_sources(bareos-fd PRIVATE ${CMAKE_CURRENT_BINARY_DIR}/../win32/filed/filedres.rc) +endif() + set(BAREOS_FD_LIBRARIES bareosfind bareos Threads::Threads) if(HAVE_WIN32) target_sources(bareos-fd PRIVATE ../win32/generic/main.cc)
then the icon appears normally again.
The text was updated successfully, but these errors were encountered:
pstorz
Successfully merging a pull request may close this issue.
Problem seems to be the STATIC objects we use. If you link the resource directly to the executable
then the icon appears normally again.
The text was updated successfully, but these errors were encountered: