]> source.dussan.org Git - tigervnc.git/commit
Check the generated icons into the build tree. This solves a couple of issues: ...
authorDRC <dcommander@users.sourceforge.net>
Mon, 7 Jan 2013 22:24:01 +0000 (22:24 +0000)
committerDRC <dcommander@users.sourceforge.net>
Mon, 7 Jan 2013 22:24:01 +0000 (22:24 +0000)
commitc6eaff85c495441dccbe0a29f96410f2b7b590be
tree869946ba5731a6d8b8e5aa2ef9815148a6c218a3
parentfc3e86ebd7eba12f4d53418dc2b56d5683471650
Check the generated icons into the build tree.  This solves a couple of issues:  (1) it eliminates the build dependency on ImageMagick, which was not documented and which creates a hard-to-diagnose build failure on platforms on which it isn't available, and (2) the build was completely broken on Windows, because Windows has a convert.exe program that is part of the operating system, and the TigerVNC build system was finding this and attempting to use it to generate the icons.

git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@5024 3789f03b-4d11-0410-bbf8-ca57d06f2519
media/CMakeLists.txt
media/icons/tigervnc_16.png [new file with mode: 0644]
media/icons/tigervnc_22.png [new file with mode: 0644]
media/icons/tigervnc_24.png [new file with mode: 0644]
media/icons/tigervnc_32.png [new file with mode: 0644]
media/icons/tigervnc_48.png [new file with mode: 0644]