/trunk/main/ure/source/uretest/ |
H A D | README | 63 executable. The component first attempts to instantiate all the UNO services 71 executable. The component tries to instantiate and to call a C++ UNO component 78 java executable. The application bootstraps a native UNO environment, and then 85 javaclient.uno. The uno executable runs the cppserver.uno component which 86 listens on a pipe connection. The java executable runs the javaclient.uno 91 Checks that the regview executable of the URE installation works reliably.
|
/trunk/main/desktop/test/deployment/executable_content/ |
H A D | readme.txt | 1 When the executable is installed try to execute the executable "hello". The executable 11 Each directory contains a hello executable. On linux one should execute it in a
|
/trunk/main/testtools/ |
H A D | readme.txt | 29 removed from the uno executable call) or a modified bridgetest_javaserver (with 30 the final "singleaccept" argument replaced with "multi" in the java executable 32 added to the uno executable call). The client will continuously establish
|
/trunk/main/setup_native/scripts/ |
H A D | admin.pl | 1105 my $executable = $unopkgfile; 1106 make_absolute_filename_to_relative_filename(\$executable); 1119 $executable = "./" . $executable; 1126 my $systemcall = $executable . " sync --verbose 2\>\&1 |";
|
/trunk/main/xmerge/source/palmtests/bin/ |
H A D | README | 3 POSE2_EXE = Directory and name of the POSE executable file. 4 POSE3_EXE = Directory and name of the POSE executable file.
|
/trunk/main/ucb/source/ucp/webdav/ |
H A D | DAVTypes.hxx | 58 bool executable; // supports "executable" property (introduced by mod_dav) member 60 DAVCapabilities() : class1( false ), class2( false ), executable( false ) {} in DAVCapabilities()
|
/trunk/main/desktop/source/deployment/ |
H A D | dp_services.cxx | 56 namespace executable { namespace 101 dp_registry::backend::executable::serviceDecl, in component_getFactory()
|
/trunk/main/testtools/qa/cli/ |
H A D | readme.txt | 17 which reside next to the executable. The testtools project copies the assemblies from 25 When the test fails one should directly run that executable. Then one may see the cause
|
/trunk/main/solenv/doc/gbuild/solenv/gbuild/ |
H A D | sdi.mk | 37 /// The target on with to depend to make sure the svidl executable is available. 39 …to depend to make sure the auxiliary files (libraries etc.) for the svidl executable are available.
|
/trunk/main/udkapi/com/sun/star/lang/ |
H A D | XMain.idl | 41 /** Executing interface for executable components run by the uno executable
|
/trunk/main/offapi/com/sun/star/system/ |
H A D | XSystemShellExecute.idl | 39 <p>This may be an executable file or a document which is registered with 42 <p>If the command specifies a path to an executable, etc, this has to be
|
/trunk/main/udkapi/com/sun/star/loader/ |
H A D | XImplementationLoader.idl | 69 their own protocol (for instance an executable loader may need 104 their own protocol (for instance an executable loader may need
|
/trunk/main/ |
H A D | bootstrap.1 | 50 #make sure build.pl is executable 149 # Deploy the dmake executable to solenv
|
/trunk/main/ure/source/ |
H A D | README | 186 - uno is the executable file that runs UNO components. For more details, see 283 When a URE executable, such as uno, starts a Java VM, the URE Java Framework 289 installation. When an executable tries to start a Java VM, the URE searches the 356 C++ UNO components run from within the uno executable can depend on an
|
/trunk/main/desktop/test/deployment/executable_content/build/ |
H A D | readme.txt | 1 This folder contains the sources to build the hello executable which is contained
|
/trunk/main/desktop/source/deployment/registry/executable/ |
H A D | dp_executablebackenddb.hxx | 40 namespace executable { namespace
|
H A D | dp_executablebackenddb.cxx | 44 namespace executable { namespace
|
/trunk/main/stoc/test/registry_tdprovider/ |
H A D | readme.txt | 3 the uno executable to a stand-alone application that bootstraps UNO in a special
|
/trunk/main/stoc/test/tdmanager/ |
H A D | readme.txt | 3 the uno executable to a stand-alone application that bootstraps UNO in a special
|
/trunk/main/extensions/test/ole/OleClient/ |
H A D | readme.txt | 6 types.rdb and services.rdb and OleClient.ini have to be next to the executable.
|
/trunk/main/saxon/ |
H A D | saxon-9.0.0.7-bj.patch | 618 + <exec dir="." executable="ikvmc.cmd" > 632 + <exec dir="." executable="csharp-compile.cmd" > 646 + executable="${csharp.compiler}" 657 + executable="${csharp.compiler}" 670 …target name="basic-userdoc" description="Generate Basic Documentation for release with executable">
|
/trunk/main/sal/test/unloading/ |
H A D | readme.txt | 4 The makefile produces the executable unloading.exe as wells as two
|
/trunk/main/toolkit/src2xml/ |
H A D | README | 6 The main executable file is located in ./source/src2xml.py. Run
|
/trunk/main/extensions/test/ole/OleConverterVar1/ |
H A D | readme.txt | 6 The executable needs a services.rdb present with the registered services
|
/trunk/main/solenv/bin/ |
H A D | packmodule | 42 (executable, outdir, module) = args
|