Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Great, thank you! Robert, could you please try the nightly to see if there are any further issues preventing you from using the latest Nsight Tegra? -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Wednesday, December 17, 2014 7:20 PM To: Dmitry Polyanitsa Cc: Robert Goulet; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/17/2014 09:22 AM, Dmitry Polyanitsa wrote: > adds ANDROID_API_MIN/CMAKE_ANDROID_API_MIN which will allow you to set > the Min Android API Level in your projects. Thanks. I've applied the patch and merged for testing: Add 'ANDROID_API_MIN' target property to set Android Target MIN API http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eeaa25e5 This will be available in the next nightly binaries that appear here: http://www.cmake.org/files/dev/?C=M;O=D We're long past the freeze for 3.1 features so this will be in 3.2. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
On 12/17/2014 09:22 AM, Dmitry Polyanitsa wrote: > adds ANDROID_API_MIN/CMAKE_ANDROID_API_MIN which will allow you > to set the Min Android API Level in your projects. Thanks. I've applied the patch and merged for testing: Add 'ANDROID_API_MIN' target property to set Android Target MIN API http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=eeaa25e5 This will be available in the next nightly binaries that appear here: http://www.cmake.org/files/dev/?C=M;O=D We're long past the freeze for 3.1 features so this will be in 3.2. -Brad -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
No, you're right - this is an unfortunate shortcoming. I've attached a patch for CMake as of 0dd9e71 that adds ANDROID_API_MIN/CMAKE_ANDROID_API_MIN which will allow you to set the Min Android API Level in your projects. Brad, I've used ANDROID_API/CMAKE_ANDROID_API as an example when implementing this change. I've added "MIN" as a postfix, for it seemed to be the preferred way, judging by the other propertiy names. Could you please merge the patch into CMake? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Tuesday, December 16, 2014 7:36 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Yes but in our case, we target API 19 (4.4), and min seems to defaults to 9 (2.3) with CMake, and if we leave the native API to use the min, then it fails to find GLES 3.0 headers. It only works if I set the native API to Target instead of Min. Perhaps I misunderstood something? -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 11:09 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Native Android API Level really should be the same as Min Android API Level, otherwise you might have problems in runtime. The upgrade action sets this property to Use Target Android API Level only for the sake of compatibility between Nsight Tegra versions, but we strongly encourage our users to switch it back to Use Min. We will show a warning if the Native and Min API Levels are not the same (Google's ndk-build does it as well). -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Tuesday, December 16, 2014 6:58 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Upgrading to CMake 3.1-rc3 indeed fixed the upgrade popup upon opening generated solution/project files when using NVidia NSight Tegra 3.0r4, however the value of "Native Android API Level" seems to default to "Use Min Android API Level" instead of the expected "Use Target Android API Level". Since we cannot set the Min or the Native API Level explicitly in CMake, this is a regression when upgrading to NVidia NSight Tegra 3.0r4 (from 3.0r3). I guess we will have to stick with NVidia NSight Tegra 3.0r3 for now. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 8:46 AM To: Brad King; Robert Goulet Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Yes, that's the one. Nsight Tegra will upgrade the projects without a prompt, but only starting with the next version number increase. -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 16, 2014 4:30 PM To: Robert Goulet Cc: Dmitry Polyanitsa; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this - please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- 0001-Add-ANDROID_API_MIN-target-property-and-CMAKE_ANDROI.patch Description: 0001-Add-ANDROID_API_MIN-target-property-and-CMAKE_ANDROI.patch -- 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
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Yes but in our case, we target API 19 (4.4), and min seems to defaults to 9 (2.3) with CMake, and if we leave the native API to use the min, then it fails to find GLES 3.0 headers. It only works if I set the native API to Target instead of Min. Perhaps I misunderstood something? -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 11:09 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Native Android API Level really should be the same as Min Android API Level, otherwise you might have problems in runtime. The upgrade action sets this property to Use Target Android API Level only for the sake of compatibility between Nsight Tegra versions, but we strongly encourage our users to switch it back to Use Min. We will show a warning if the Native and Min API Levels are not the same (Google's ndk-build does it as well). -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Tuesday, December 16, 2014 6:58 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Upgrading to CMake 3.1-rc3 indeed fixed the upgrade popup upon opening generated solution/project files when using NVidia NSight Tegra 3.0r4, however the value of "Native Android API Level" seems to default to "Use Min Android API Level" instead of the expected "Use Target Android API Level". Since we cannot set the Min or the Native API Level explicitly in CMake, this is a regression when upgrading to NVidia NSight Tegra 3.0r4 (from 3.0r3). I guess we will have to stick with NVidia NSight Tegra 3.0r3 for now. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 8:46 AM To: Brad King; Robert Goulet Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Yes, that's the one. Nsight Tegra will upgrade the projects without a prompt, but only starting with the next version number increase. -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 16, 2014 4:30 PM To: Robert Goulet Cc: Dmitry Polyanitsa; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this - please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Native Android API Level really should be the same as Min Android API Level, otherwise you might have problems in runtime. The upgrade action sets this property to Use Target Android API Level only for the sake of compatibility between Nsight Tegra versions, but we strongly encourage our users to switch it back to Use Min. We will show a warning if the Native and Min API Levels are not the same (Google's ndk-build does it as well). -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Tuesday, December 16, 2014 6:58 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Upgrading to CMake 3.1-rc3 indeed fixed the upgrade popup upon opening generated solution/project files when using NVidia NSight Tegra 3.0r4, however the value of "Native Android API Level" seems to default to "Use Min Android API Level" instead of the expected "Use Target Android API Level". Since we cannot set the Min or the Native API Level explicitly in CMake, this is a regression when upgrading to NVidia NSight Tegra 3.0r4 (from 3.0r3). I guess we will have to stick with NVidia NSight Tegra 3.0r3 for now. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 8:46 AM To: Brad King; Robert Goulet Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Yes, that's the one. Nsight Tegra will upgrade the projects without a prompt, but only starting with the next version number increase. -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 16, 2014 4:30 PM To: Robert Goulet Cc: Dmitry Polyanitsa; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this - please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Upgrading to CMake 3.1-rc3 indeed fixed the upgrade popup upon opening generated solution/project files when using NVidia NSight Tegra 3.0r4, however the value of "Native Android API Level" seems to default to "Use Min Android API Level" instead of the expected "Use Target Android API Level". Since we cannot set the Min or the Native API Level explicitly in CMake, this is a regression when upgrading to NVidia NSight Tegra 3.0r4 (from 3.0r3). I guess we will have to stick with NVidia NSight Tegra 3.0r3 for now. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Tuesday, December 16, 2014 8:46 AM To: Brad King; Robert Goulet Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Yes, that's the one. Nsight Tegra will upgrade the projects without a prompt, but only starting with the next version number increase. -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 16, 2014 4:30 PM To: Robert Goulet Cc: Dmitry Polyanitsa; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this - please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Set_source_files_properties( *test2.c** PROPERTIES** LANGUAGE CXX** )* http://www.cmake.org/pipermail/cmake/2008-July/022647.html On Tue, Dec 16, 2014 at 5:45 AM, Dmitry Polyanitsa wrote: > > Yes, that's the one. > > Nsight Tegra will upgrade the projects without a prompt, but only starting > with the next version number increase. > > -Dmitry > > -Original Message- > From: Brad King [mailto:brad.k...@kitware.com] > Sent: Tuesday, December 16, 2014 4:30 PM > To: Robert Goulet > Cc: Dmitry Polyanitsa; cmake-developers@cmake.org > Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions > and output names > > On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: > >> 3.0r4 has added a popup when opening the solution in Visual Studio > >> stating that the project files generated needs to be upgraded. > > > > I'm sure I've submitted a patch for this - please try updating CMake > > IIUC the patch was this one: > > VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 > http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 > > and is available in 3.1.0-rc3. > > However, CMake cannot predict future version numbers, so it writes a > "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. > Nsight Tegra is supposed to upgrade such projects without any popup. > > -Brad > > > --- > This email message is for the sole use of the intended recipient(s) and > may contain > confidential information. Any unauthorized review, use, disclosure or > distribution > is prohibited. If you are not the intended recipient, please contact the > sender by > reply email and destroy all copies of the original message. > > --- > -- > > 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-developers > -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Yes, that's the one. Nsight Tegra will upgrade the projects without a prompt, but only starting with the next version number increase. -Dmitry -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 16, 2014 4:30 PM To: Robert Goulet Cc: Dmitry Polyanitsa; cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this - please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
On 12/16/2014 06:58 AM, Dmitry Polyanitsa wrote: >> 3.0r4 has added a popup when opening the solution in Visual Studio >> stating that the project files generated needs to be upgraded. > > I'm sure I've submitted a patch for this – please try updating CMake IIUC the patch was this one: VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=bb3c87f1 and is available in 3.1.0-rc3. However, CMake cannot predict future version numbers, so it writes a "NsightTegraUpgradeOnceWithoutPrompt" element into the project file. Nsight Tegra is supposed to upgrade such projects without any popup. -Brad -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Hi Robert, > I just tried to upgrade to 3.0r4 and it still defaults the Visual Project > setting of "Language -> C++ Language Standard" to "Default". I need to set it > to C++11 somehow, otherwise I get many errors that the C++11 code we are > using in our engine cannot compile. This will either need to be fixed in > CMake through a new variable or in the NVidia NSight Tegra package? I was wrong about this. We're using C++11 by default only in our template projects, the default value still being left up to the compiler to decide (== don't pass the standard-changing flags). I'm afraid for the time being you'll need to use the workaround you've already mentioned. We'll probably add some Nsight Tegra specific properties to CMake in the future and when we do, we'll make sure C++ Language Standard will be one of them. > Furthermore, upgrading to 3.0r4 has added a popup when opening the solution > in Visual Studio, stating that the project files generated needs to be > upgraded. Its upgrading the setting "Preserve native API level" to some > value. My guess it that the CMake generator doesn't set the proper default > value for this version of NSight. I'm sure I've submitted a patch for this - please try updating CMake to a newer RC or nightly and see if the problem goes away. -Dmitry From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Tuesday, December 16, 2014 12:02 AM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Dmitry, I just tried to upgrade to 3.0r4 and it still defaults the Visual Project setting of "Language -> C++ Language Standard" to "Default". I need to set it to C++11 somehow, otherwise I get many errors that the C++11 code we are using in our engine cannot compile. This will either need to be fixed in CMake through a new variable or in the NVidia NSight Tegra package? Furthermore, upgrading to 3.0r4 has added a popup when opening the solution in Visual Studio, stating that the project files generated needs to be upgraded. Its upgrading the setting "Preserve native API level" to some value. My guess it that the CMake generator doesn't set the proper default value for this version of NSight. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 11:14 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names We usually advise to upgrade to the latest version. The transition should be smooth, but you may want to install TADP 3.0r4 on one of the machines first to check all's good before updating it everywhere. In case of any issues or questions you can contact me directly via email. -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 7:03 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names We are currently using 3.0-r3, and I am guessing this version doesn't use C++11 by default. You are saying that the latest release should fix this, because it defaults to C++11? I am not sure what are the implications of upgrading our engine with this new version. Should we expect the transition to go smoothly? We have to decide on a final version for the release, what's your thoughts on this? Thanks! -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 10:46 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, I'm Dmitry from the Nsight Tegra team. Currently, we do not allow changing the APK name, so copying/moving the outputs is the best you can do. As for the language standard override, latest Nsight Tegra uses C++11 by default, why would you want to set it explicitly? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 12:28 AM To: Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake res
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Hi Dmitry, I just tried to upgrade to 3.0r4 and it still defaults the Visual Project setting of "Language -> C++ Language Standard" to "Default". I need to set it to C++11 somehow, otherwise I get many errors that the C++11 code we are using in our engine cannot compile. This will either need to be fixed in CMake through a new variable or in the NVidia NSight Tegra package? Furthermore, upgrading to 3.0r4 has added a popup when opening the solution in Visual Studio, stating that the project files generated needs to be upgraded. Its upgrading the setting "Preserve native API level" to some value. My guess it that the CMake generator doesn't set the proper default value for this version of NSight. -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 11:14 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names We usually advise to upgrade to the latest version. The transition should be smooth, but you may want to install TADP 3.0r4 on one of the machines first to check all's good before updating it everywhere. In case of any issues or questions you can contact me directly via email. -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 7:03 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names We are currently using 3.0-r3, and I am guessing this version doesn't use C++11 by default. You are saying that the latest release should fix this, because it defaults to C++11? I am not sure what are the implications of upgrading our engine with this new version. Should we expect the transition to go smoothly? We have to decide on a final version for the release, what's your thoughts on this? Thanks! -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 10:46 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, I'm Dmitry from the Nsight Tegra team. Currently, we do not allow changing the APK name, so copying/moving the outputs is the best you can do. As for the language standard override, latest Nsight Tegra uses C++11 by default, why would you want to set it explicitly? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 12:28 AM To: Brad King Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake result or if its NVidia's Tegra toolkit? But I have a work-around for that, using add_custom_command to do a copy using ${CMAKE_COMMAND} -E copy. So my only issue left is the fact that I will have to use set_source_properties to pass the -std=c++11 flag instead of being able to set the "C++ Language Standard" option. That is a bit annoying, is there a better work-around? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 2, 2014 3:45 PM To: Robert Goulet Cc: cmake-developers@cmake.org<mailto:cmake-developers@cmake.org> Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that refers to > the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect the names > that we set using the target properties OUTPUT_NAME_. Right > now it uses the project's name for the .apk, while the .so does indeed > respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
We usually advise to upgrade to the latest version. The transition should be smooth, but you may want to install TADP 3.0r4 on one of the machines first to check all's good before updating it everywhere. In case of any issues or questions you can contact me directly via email. -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 7:03 PM To: Dmitry Polyanitsa; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names We are currently using 3.0-r3, and I am guessing this version doesn't use C++11 by default. You are saying that the latest release should fix this, because it defaults to C++11? I am not sure what are the implications of upgrading our engine with this new version. Should we expect the transition to go smoothly? We have to decide on a final version for the release, what's your thoughts on this? Thanks! -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 10:46 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, I'm Dmitry from the Nsight Tegra team. Currently, we do not allow changing the APK name, so copying/moving the outputs is the best you can do. As for the language standard override, latest Nsight Tegra uses C++11 by default, why would you want to set it explicitly? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 12:28 AM To: Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake result or if its NVidia's Tegra toolkit? But I have a work-around for that, using add_custom_command to do a copy using ${CMAKE_COMMAND} -E copy. So my only issue left is the fact that I will have to use set_source_properties to pass the -std=c++11 flag instead of being able to set the "C++ Language Standard" option. That is a bit annoying, is there a better work-around? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 2, 2014 3:45 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that refers to > the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect the names > that we set using the target properties OUTPUT_NAME_. Right > now it uses the project's name for the .apk, while the .so does indeed > respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be needed too. We have RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, and ARCHIVE_OUTPUT_DIRECTORY already. I'm not sure if one of these should apply to the .apk, or if another setting would be needed. Also the availability of Nsight Tegra settings for this needs to be investigated. > C++ Language Standard to other values than Default? I don't think there is currently. The commit adding the original support was: VS: Teach vcxproj generation about the Tegra-Android platform http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef0fd4f0 The commit message documents many of the limitations. Only the last bullet (ANDROID_GUI prop) and part of the second bullet (ANDROID_API prop) have been addressed so far. The lack of a flag table or other controls for the rest of the project settings is currently the main limitation. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
We are currently using 3.0-r3, and I am guessing this version doesn't use C++11 by default. You are saying that the latest release should fix this, because it defaults to C++11? I am not sure what are the implications of upgrading our engine with this new version. Should we expect the transition to go smoothly? We have to decide on a final version for the release, what's your thoughts on this? Thanks! -Original Message- From: Dmitry Polyanitsa [mailto:dpolyani...@nvidia.com] Sent: Wednesday, December 3, 2014 10:46 AM To: Robert Goulet; Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, I'm Dmitry from the Nsight Tegra team. Currently, we do not allow changing the APK name, so copying/moving the outputs is the best you can do. As for the language standard override, latest Nsight Tegra uses C++11 by default, why would you want to set it explicitly? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 12:28 AM To: Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake result or if its NVidia's Tegra toolkit? But I have a work-around for that, using add_custom_command to do a copy using ${CMAKE_COMMAND} -E copy. So my only issue left is the fact that I will have to use set_source_properties to pass the -std=c++11 flag instead of being able to set the "C++ Language Standard" option. That is a bit annoying, is there a better work-around? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 2, 2014 3:45 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that refers to > the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect the names > that we set using the target properties OUTPUT_NAME_. Right > now it uses the project's name for the .apk, while the .so does indeed > respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be needed too. We have RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, and ARCHIVE_OUTPUT_DIRECTORY already. I'm not sure if one of these should apply to the .apk, or if another setting would be needed. Also the availability of Nsight Tegra settings for this needs to be investigated. > C++ Language Standard to other values than Default? I don't think there is currently. The commit adding the original support was: VS: Teach vcxproj generation about the Tegra-Android platform http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef0fd4f0 The commit message documents many of the limitations. Only the last bullet (ANDROID_GUI prop) and part of the second bullet (ANDROID_API prop) have been addressed so far. The lack of a flag table or other controls for the rest of the project settings is currently the main limitation. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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.kitwa
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Hi Robert, I'm Dmitry from the Nsight Tegra team. Currently, we do not allow changing the APK name, so copying/moving the outputs is the best you can do. As for the language standard override, latest Nsight Tegra uses C++11 by default, why would you want to set it explicitly? -Dmitry -Original Message- From: Robert Goulet [mailto:robert.gou...@autodesk.com] Sent: Wednesday, December 3, 2014 12:28 AM To: Brad King Cc: cmake-developers@cmake.org Subject: RE: [cmake-developers] CMake 3.1 Android - generator expressions and output names I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake result or if its NVidia's Tegra toolkit? But I have a work-around for that, using add_custom_command to do a copy using ${CMAKE_COMMAND} -E copy. So my only issue left is the fact that I will have to use set_source_properties to pass the -std=c++11 flag instead of being able to set the "C++ Language Standard" option. That is a bit annoying, is there a better work-around? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 2, 2014 3:45 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that refers to > the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect the names > that we set using the target properties OUTPUT_NAME_. Right > now it uses the project's name for the .apk, while the .so does indeed > respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be needed too. We have RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, and ARCHIVE_OUTPUT_DIRECTORY already. I'm not sure if one of these should apply to the .apk, or if another setting would be needed. Also the availability of Nsight Tegra settings for this needs to be investigated. > C++ Language Standard to other values than Default? I don't think there is currently. The commit adding the original support was: VS: Teach vcxproj generation about the Tegra-Android platform http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef0fd4f0 The commit message documents many of the limitations. Only the last bullet (ANDROID_GUI prop) and part of the second bullet (ANDROID_API prop) have been addressed so far. The lack of a flag table or other controls for the rest of the project settings is currently the main limitation. -Brad --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
I can't find any options to set the .apk name from the IDE, but I find it interesting that it uses the project's name instead of the output file name set in the IDE. Hence why I wonder if its CMake result or if its NVidia's Tegra toolkit? But I have a work-around for that, using add_custom_command to do a copy using ${CMAKE_COMMAND} -E copy. So my only issue left is the fact that I will have to use set_source_properties to pass the -std=c++11 flag instead of being able to set the "C++ Language Standard" option. That is a bit annoying, is there a better work-around? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, December 2, 2014 3:45 PM To: Robert Goulet Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that refers to > the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect the names > that we set using the target properties OUTPUT_NAME_. Right > now it uses the project's name for the .apk, while the .so does indeed > respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be needed too. We have RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, and ARCHIVE_OUTPUT_DIRECTORY already. I'm not sure if one of these should apply to the .apk, or if another setting would be needed. Also the availability of Nsight Tegra settings for this needs to be investigated. > C++ Language Standard to other values than Default? I don't think there is currently. The commit adding the original support was: VS: Teach vcxproj generation about the Tegra-Android platform http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef0fd4f0 The commit message documents many of the limitations. Only the last bullet (ANDROID_GUI prop) and part of the second bullet (ANDROID_API prop) have been addressed so far. The lack of a flag table or other controls for the rest of the project settings is currently the main limitation. -Brad -- 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-developers
Re: [cmake-developers] CMake 3.1 Android - generator expressions and output names
Hi Robert, Thanks for trying out the Nsight Tegra generator support. It is brand new so we are just at the beginning of the maturation process. We would appreciate any help you can provide. On 12/02/2014 02:24 PM, Robert Goulet wrote: > Perhaps it would be nice to have a generator expression that > refers to the .apk file produced when compiling for Android? This may be possible, but first we should work out the output name and location settings as discussed next. > Also, it would make sense that the .apk output name respect > the names that we set using the target properties > OUTPUT_NAME_. Right now it uses the project's name for the > .apk, while the .so does indeed respect the output name set. Is it possible to configure the .apk name through the IDE? If so, CMake could be taught to add the corresponding setting to the .vcxproj file. If not, then Nsight Tegra itself would have to be modified by NVIDIA to support such a setting. Some output directory settings may be needed too. We have RUNTIME_OUTPUT_DIRECTORY, LIBRARY_OUTPUT_DIRECTORY, and ARCHIVE_OUTPUT_DIRECTORY already. I'm not sure if one of these should apply to the .apk, or if another setting would be needed. Also the availability of Nsight Tegra settings for this needs to be investigated. > C++ Language Standard to other values than Default? I don't think there is currently. The commit adding the original support was: VS: Teach vcxproj generation about the Tegra-Android platform http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=ef0fd4f0 The commit message documents many of the limitations. Only the last bullet (ANDROID_GUI prop) and part of the second bullet (ANDROID_API prop) have been addressed so far. The lack of a flag table or other controls for the rest of the project settings is currently the main limitation. -Brad -- 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-developers
[cmake-developers] CMake 3.1 Android - generator expressions and output names
Perhaps it would be nice to have a generator expression that refers to the .apk file produced when compiling for Android? Also, it would make sense that the .apk output name respect the names that we set using the target properties OUTPUT_NAME_. Right now it uses the project's name for the .apk, while the .so does indeed respect the output name set. Thoughts? While discussing about CMake Android support... is there a way to set the Visual Studio property C/C++ -> Language -> C++ Language Standard to other values than Default? I would like to set it to C++11. Unfortunately, setting -std=c++11 on the command line generates the error "invalid argument '-std=c++11' not allowed with 'C/ObjC'", and it would be super annoying to go and set this flag for each cpp files manually because we are using a lot of projects. -- 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-developers