path: root/cli_ure/
diff options
authorMichael Stahl <>2013-09-21 01:35:41 +0200
committerMichael Stahl <>2013-09-22 11:08:32 +0200
commit814ec7640fc2a529343e358ab4fd3b9a59d645ca (patch)
tree0462df8c1f5dc24f4d65be6b01c1f297d570a8f0 /cli_ure/
parent4ac934946e1e02fc000c56f23575c766c7a912d1 (diff)
cli_ure: copy cli_basetypes to INSTDIR/sdk/bin
The library is already in the URE/bin directory, but that is not sufficient to be able to run sdk/bin/climaker.exe. There are apparently 4 ways for a .net/CLR executable to locate shared libraries: 1) in the same directory as the executable 2) in some mysterious "GAC" thing in C:/Windows (which is presumably how it works if you actually install LO) 3) via an application configuration file entry "probing", which only works when it's in a sub-directory of the one the executable is in 4) via a DEVPATH variable, but that only works with a special configuration entry in a system "machine config" file of the .net framework Specifically PATH is apparently ignored. Since building on Windows is enough of a PITA already and we don't want developers to have to edit another config file, put another copy of the library into sdk/bin. Change-Id: I511957ad9a9a918ed0c316126304a1980fb2d289
Diffstat (limited to 'cli_ure/')
1 files changed, 4 insertions, 0 deletions
diff --git a/cli_ure/ b/cli_ure/
index db7e42ccdc7e..f1aaf62914ae 100644
--- a/cli_ure/
+++ b/cli_ure/
@@ -9,6 +9,10 @@
$(eval $(call gb_Executable_Executable,climaker))
+$(eval $(call gb_Executable_use_package,climaker,\
+ cli_basetypes_copy \
$(eval $(call gb_Executable_add_cxxflags,climaker,\
-AI $(gb_Helper_OUTDIRLIBDIR) \
-clr \