forked from amazingfate/loongoffice
It used to be mis-spelled PATH_SEPERATOR. Now, after correcting the spelling, it breaks the build of 3rd-party libraries using autoconfigury on Windows. The value of PATH_SEPARATOR is ";" on Windows, and the configure scripts of those libs run in Cygwin and assume that a PATH_SEPARATOR environment variable should be correct for Cygwin. Which ";" isn't. Rename the variable to LIBO_PATH_SEPARATOR. Change-Id: Iff0eb93bf11d9f844a28be7ea4456e4c0ae10844
# # 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 . # Test that a Java URP bridge started in a native process uses the same thread pool as a C++ URP bridge. This test currently only works on Linux Intel. There are two processes involved. The client starts as a native process. It first loads a Java component (Relay) via the in-process JNI bridge, which in turn starts to accept incomming URP connections. The native part of the client then connects to the server, retrieves a thread-local token from it, and checks the token for correctness. The server simply waits for a connection from the native part of the client, creates a connection to the Java part of the client, and routes all requests from the native part of the client to the Java part of the client. The Java part of the client in turn uses the in-process JNI bridge to obtain the thread-local token.