strepsirrhini/office-gobmx
9
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
office-gobmx/ure/source/uretest/README
Stephan Bergmann 40f2aee658 Provide unoidl-write also for the SDK 
...after the new types.rdb format that unoidl-write generates has been used
internally since LibreOffice 4.1 in 2013; following up on
6db34b6b33 "Directly build UNOIDL .rdb files from
.idl files" and its "The legacy tools idlc, regcompare, regmerge, and regview
are still contained in the URE or SDK for now."

The tools idlc and regmerge are deprecated but still shipped in the SDK for now.
The plan is to drop them completely for LO 7.5.

odk/examples/ and ure/source/uretest/ are adapted to use unoidl-write instead of
idlc and regmerge:

* unoidl-write does not use a C preprocessor and the # directives in .idl files,
  it supports reading a single .idl file (containing an arbitrary number of
  declarations) or a directory tree where each directory corresponds to a UNOIDL
  module of the same name and each .idl file contains the declaration of the
  (non-module) UNOIDL entity of the same name.  For some of the odk/examples/,
  that required moving individual .idl files into sub-directories named after
  the respective modules.  In odk/settings/std.mk, definitinos of IDL and
  REGMERGE have been replaced with a new UNOIDLWRITE.

* unoidl-write always enforces reserved UNOIDL identifier restrictions (see
  04af4e4f55 "[API CHANGE] Fix all bad UNOIDL
  identifiers across offapi" and 6201792406
  "Enforce the UNOIDL identifier scheme") (which idlc only enforced optionally
  with -cid -we).  That required renaming "my_module" in
  odk/examples/DevelopersGuide/Components/CppComponent/.

* The new types.rdb format is not compatibly with LibreOffice < 4.1.  Clients
  generating extensions containing such files are advised to use appropriate
  LibreOffice-minimal-version elements.

Change-Id: I1a248fd96e86ecbf407f829bc100d44bfe7f4e7d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/130533
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
2022-02-25 16:46:26 +01:00

101 lines
4.3 KiB
Text
Raw Blame History

#
# 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/.
#
# This file incorporates work covered by the following license notice:
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements. See the NOTICE file distributed
# with this work for additional information regarding copyright
# ownership. The ASF licenses this file to you under the Apache
# License, Version 2.0 (the "License"); you may not use this file
# except in compliance with the License. You may obtain a copy of
# the License at http://www.apache.org/licenses/LICENSE-2.0 .
#
This directory contains test files for the UNO Runtime Environment (URE) as well
as the Makefile and Makefile.pln makefiles. To execute the makefiles, you need
GNU make 3.80 or later.
Makefile
--------
Before you execute Makefile, you need to configure the Software Development Kit
(SDK) environment to work with a URE installation, a C++ compiler, and a JDK.
For more information, read the .../docs/install.html file in the SDK
installation.
NOTE: On Linux x86, if the Makefile accesses a GCC that is incompatible with the
GCC that was used to build the URE, use the GCCS_COMPAT environment variable as
a workaround. For more details, see the UDK README file.
Makefile.pln
------------
You can only run Makefile.pln on Linux x86. You do not need to configure your
SDK environment to use this makefile, however, you do need to set the following
environment variables:
- SDK_HOME
Points to the base directory of an OpenOffice.org SDK so that you can access UNO
programming tools and files that are not part of the URE. For example, unoidl-write,
cppumaker, javamaker, and C++ headers.
- PATH
Points to a GCC installation (including g++) as well as a JDK installation that
contains the java, javac, and jar executables. For the minimum version
requirements, see the SDK Installation Guide ($SDK_HOME/docs/install.html).
- URE_HOME (optional)
Overwrites the default URE location, that is, /opt/libreoffice.
- GCCS_COMPAT (optional)
Fixes incompatibility issues between the GCC that was used to build the URE and
the GCC that Makefile.pln accesses. For more details, see the UDK README file.
Tests
-----
Makefile and Makefile.pln can execute the following tests:
- test-cpptest
Builds a C++ UNO component, cppmain.uno, and runs the component with the uno
executable. The component first attempts to instantiate all the UNO services
and singletons that are part of the URE installation. The component then tries
to instantiate and to call another C++ UNO component (cpptest.uno) as well as a
Java UNO component (javatest.uno). The test completes when these components
throw a special exception that is caught by cppmain.uno.
- test-javatest
Builds a Java UNO component, javamain.uno, and runs the component with the uno
executable. The component tries to instantiate and to call a C++ UNO component
(cpptest.uno) as well as a Java UNO component (javatest.uno). The test
completes when these components throw a special exception that is caught by
javamain.uno.
- test-javanative
Builds a Java UNO application, javanative.jar, and runs the application with the
java executable. The application bootstraps a native UNO environment, and then
tries to instantiate and to call a C++ UNO component (cpptest.uno) as well as a
Java UNO component( javatest.uno). The test completes when these components
throw a special exception that is caught by javanative.jar.
- test-clientserver
Builds a server C++ UNO component, cppserver.uno, and a Java UNO application,
javaclient.uno. The uno executable runs the cppserver.uno component which
listens on a pipe connection. The java executable runs the javaclient.uno
component which connects to the server after a five second pause so that the
server has enough time to start.
- test-regview (Makefile.pln only)
Checks that the regview executable of the URE installation works reliably.
NOTE: The files that are generated when Makefile and Makefile.pln execute are
saved to different local directories. Makefile outputs the generated files to
./out.sdk whereas Makefile.pln outputs the files to ./out.pln.
Reference in a new issue View git blame Copy permalink