This website requires JavaScript.
Explore
Help
Sign In
mirrors
/
FreeRDP
Watch
1
Star
0
Fork
0
You've already forked FreeRDP
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
3a5fdd0a39
FreeRDP
/
server
/
.gitignore
10 lines
75 B
Plaintext
Raw
Normal View
History
Unescape
Escape
freerdp: remove vendor-specific options from build system, add automatic ways of including external clients/servers
2013-09-04 04:37:04 +04:00
/*
!/common
!/Mac
!/Sample
!/Windows
!/X11
shadow: start simplifying X11 shadow server
2014-07-11 00:32:46 +04:00
!/shadow
freerdp: remove vendor-specific options from build system, add automatic ways of including external clients/servers
2013-09-04 04:37:04 +04:00
!/CmakeLists.txt
cleanup cmake exports and pkg-config files With this commit the "exported" components (usable with pkg-config and cmake find module package) * winpr - winpr library and headers * freerdp - core library and headers * freerdp-client - client specific library * freerdp-server - server specific library * rdtk - rdtk headers and library To allow the installation of multiple different version (different major number) the include files were moved into the respective sub folder: freerdp -> freerdp{MAJOR}/freerdp (currently freerdp2/freerdp/) winpr -> winpr{MAJOR}/winpr (currently winrp1/winpr/) rdtk -> rdpk{MAJOR}/rdtk (currently rdtk0/rdtk/ The generated pkg-config and cmake find modules now also include the major version number. Currently the following pkg-config are generated and installed. * winpr1 * freerdp2 * freerdp-server2 * freerdp-client2 * rdtk0 As cmake is able to handle multiple versions out of the box the following can be used to find a specific module: find_package(WinPR) find_package(FreeRDP) find_package(FreeRDP-Server) find_package(FreeRDP-Client) find_package(RdTk) As cmake doesn't automatically resolve dependencies for packages it is necessary to manually include the requirements. For example if FreeRDP-Client is required WinPR and FreeRDP need to be included (find_package) as well. This commit also fixes the installation when STATIC_CHANNELS are built. WITH STATIC_CHANNELS all channels are linked into libfreerdp-client, for this all channels are generated as linker archive and linked together in the final step. Before the intermediate linker archives were, although not required and useful, installed. Same applies for server side channels.
2016-01-08 16:07:35 +03:00
!*.in
Reference in New Issue
Copy Permalink