# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*- # # This file is part of the LibreOffice project. # # This Source Code Form is subject to the terms of the Mozilla Public # License, v. 2.0. If a copy of the MPL was not distributed with this # file, You can obtain one at http://mozilla.org/MPL/2.0/. # $(eval $(call gb_CppunitTest_CppunitTest,svgio)) $(eval $(call gb_CppunitTest_set_componentfile,svgio,svgio/svgio)) $(eval $(call gb_CppunitTest_set_include,svgio,\ $$(INCLUDE) \ -I$(SRCDIR)/svgio/inc \ )) $(eval $(call gb_CppunitTest_use_externals,svgio,\ boost_headers \ libxml2 \ )) $(eval $(call gb_CppunitTest_use_sdk_api,svgio)) $(eval $(call gb_CppunitTest_use_library_objects,svgio,\ svgio \ )) $(eval $(call gb_CppunitTest_use_libraries,svgio,\ basegfx \ drawinglayer \ cppu \ cppuhelper \ comphelper \ sal \ sax \ svt \ test \ unotest \ tl \ vcl \ $(gb_UWINAPI) \ )) $(eval $(call gb_CppunitTest_add_exception_objects,svgio,\ svgio/qa/cppunit/SvgImportTest \ )) $(eval $(call gb_CppunitTest_use_ure,svgio)) $(eval $(call gb_CppunitTest_use_vcl,svgio)) $(eval $(call gb_CppunitTest_use_components,svgio,\ configmgr/source/configmgr \ dtrans/util/mcnttype \ framework/util/fwk \ i18npool/util/i18npool \ package/source/xstor/xstor \ package/util/package2 \ toolkit/util/tk \ sfx2/util/sfx \ ucb/source/core/ucb1 \ ucb/source/ucp/file/ucpfile1 \ unotools/util/utl \ sax/source/expatwrap/expwrap \ )) $(eval $(call gb_CppunitTest_use_configuration,svgio)) # vim: set noet sw=4 ts=4: cli_ure: copy cli_basetypes to INSTDIR/sdk/bin 2013-09-22T09:08:32+00:00 Michael Stahl mstahl@redhat.com 2013-09-20T23:35:41+00:00 814ec7640fc2a529343e358ab4fd3b9a59d645ca 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. http://tutorials.csharp-online.net/.NET_CLR_Components%E2%80%94Resolving_Names_to_Locations http://tutorials.csharp-online.net/.NET_CLR_Components%E2%80%94CLR_Loader Change-Id: I511957ad9a9a918ed0c316126304a1980fb2d289
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.

http://tutorials.csharp-online.net/.NET_CLR_Components%E2%80%94Resolving_Names_to_Locations
http://tutorials.csharp-online.net/.NET_CLR_Components%E2%80%94CLR_Loader

Change-Id: I511957ad9a9a918ed0c316126304a1980fb2d289
gbuildize cli_ure 2012-09-22T06:15:23+00:00 David Tardon dtardon@redhat.com 2012-07-29T09:49:31+00:00 118cc6807d2cbdc2395d9e61beea98cecb6c0b73 Change-Id: I716d666fc6e9d5339bc65a1b3943b2cecf45b6fe
Change-Id: I716d666fc6e9d5339bc65a1b3943b2cecf45b6fe