t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index e9cca30..7384954 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20190913)
+set(CMake_VER
I will do that. It's also easier for me to track the changes that way.
Regards,
Tushar
On Sat, Sep 14, 2019 at 12:04 AM Brad King wrote:
>
> On 9/13/19 1:30 PM, Tushar Maheshwari wrote:
> > Thanks for the quick response.
> > I have my commits separated by file groups. I'll open small MRs
> >
On 9/13/19 1:30 PM, Tushar Maheshwari wrote:
> Thanks for the quick response.
> I have my commits separated by file groups. I'll open small MRs
> collecting the related groups.
Thanks. Please just keep a couple MRs open at a time so we don't
overwhelm the CI builders. After some are merged you
Thanks for the quick response.
I have my commits separated by file groups. I'll open small MRs
collecting the related groups.
Please comment if the grouping is incorrect or if a commit/diff needs
to be moved to a different branch.
Thanks,
Tushar
On Fri, Sep 13, 2019 at 10:46 PM Brad King wrote:
On 9/13/19 12:58 PM, Kyle Edwards via cmake-developers wrote:
> On Fri, 2019-09-13 at 22:08 +0530, Tushar Maheshwari wrote:
>> I have pushed some sample commits to
>> https://gitlab.kitware.com/tusharpm/cmake/commits/smart_mem.
>>
>> If this is something I can pursue, I would appreciate a review
On Fri, 2019-09-13 at 22:08 +0530, Tushar Maheshwari wrote:
> Hi,
>
> I am a C++ developer and a modern-C++ enthusiast. In the interest of
> modernizing the codebase, I propose using smart pointers to handle
> dynamically allocated memory. I would like to get the feedback from
> the developers if
Hi,
I am a C++ developer and a modern-C++ enthusiast. In the interest of
modernizing the codebase, I propose using smart pointers to handle
dynamically allocated memory. I would like to get the feedback from
the developers if this change is planned/attempted/desirable or
inapplicable for CMake.
On Fri, 2019-09-13 at 15:25 +, Stephen Morris wrote:
> Suppose I have a class that derives from QObject, and contains the
> Q_OBJECT macro in its header file. When I compile it using AUTOMOC
> enabled, a "moc_myClass.cpp" file is created; if I manually include
> that file at the end of my
Suppose I have a class that derives from QObject, and contains the Q_OBJECT
macro in its header file. When I compile it using AUTOMOC enabled, a
"moc_myClass.cpp" file is created; if I manually include that file at the end
of my 'myClass.cpp" file, then the moc file will be compiled there,
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 19bcdca93c3a05db12652677f8d0e310797bb375 (commit)
via
For completeness, there is also OPTION C:
set_property(TARGET target PROPERTY INTERFACE_INCLUDE_DIRECTORIES
directory1 directory2)
set_target_properties() is a shorthand for setting several properties at
once, so it assumes its arguments are prop value prop value. If you need
finer control,
11 matches
Mail list logo
