--===============2051501816== Content-Type: multipart/alternative; boundary=001a113b51a48a0949050c73e9a2 --001a113b51a48a0949050c73e9a2 Content-Type: text/plain; charset=UTF-8 Hi Nils, On Mon, Jan 12, 2015 at 11:50 AM, Nils Gladitz wrote: > On 01/12/2015 11:40 AM, Andreas Pakulat wrote: > >> Ah, that works. Its a little ugly in the CMake files but I guess I can >> live with that. Ideally I was hoping to simply have a 'complete' list >> including actual sources and sources for other platforms and hand that >> to a special function - without passing the source-for-other-platform to >> the actual target. Oh well, I have to stop dreaming :) >> > > You can also use add_custom_target(my_new_target SOURCES src1.cpp > src2.cpp). > > That will list the given sources in the IDE without adding build semantics > to them. > > Since this lists the sources as part of a new target rather than an > existing target this will be visually distinct from the other approach in > some IDEs but should afaik make no difference in QtCreator. > Thanks for that idea, having a dedicated target wouldn't be so bad even if its visible. With a bit of restructuring of the cmakelists.txt this may actually make the file quite a bit more 'declarative' and less convoluted. Andreas --001a113b51a48a0949050c73e9a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Nils,

On Mon, Jan 12, 2015 at 11:50 AM, Nils Gladitz &l= t;nilsgladitz@gm= ail.com> wrote:
On 01/12/2015 11:40 AM, Andreas Pakulat wrote:
Ah, that works. Its a little ugly in the CMake files but I guess I can
live with that. Ideally I was hoping to simply have a 'complete' li= st
including actual sources and sources for other platforms and hand that
to a special function - without passing the source-for-other-platform to the actual target. Oh well, I have to stop dreaming :)

You can also use add_custom_target(my_new_target SOURCES src1.cpp sr= c2.cpp).

That will list the given sources in the IDE without adding build semantics = to them.

Since this lists the sources as part of a new target rather than an existin= g target this will be visually distinct from the other approach in some IDE= s but should afaik make no difference in QtCreator.
Thanks for that idea, having a dedicated target wouldn't b= e so bad even if its visible. With a bit of restructuring of the cmakelists= .txt this may actually make the file quite a bit more 'declarative'= and less convoluted.

Andreas=C2=A0
--001a113b51a48a0949050c73e9a2-- --===============2051501816== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake --===============2051501816==--