> On May 3, 2017, at 8:20 PM, Sean Wayland wrote:
>
> Hi all,
>
> I am very new to cmake and boost. Sorry if my question is basic thanks for
> your help in advance.
>
> I am having trouble linking a project to boost. I am using OSX 10.12.1
> I am using clion 2017.1.1
_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170503)
+set(CMake_VERSION_PATCH 20170504)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hi all,
I am very new to cmake and boost. Sorry if my question is basic thanks for
your help in advance.
I am having trouble linking a project to boost. I am using OSX 10.12.1
I am using clion 2017.1.1
I installed boost on my machine using /bootstrap.sh
--prefix=/usr/local/boost
That worked - thank you! Do I need to add NSIS manually for Windows installers
as well? It looks like CMake finds NSIS without any difficulty but I’d rather
be sure.
Thanks,
Ayla
> On May 3, 2017, at 2:56 PM, Robert Maynard wrote:
>
> You will need to append the
You will need to append the productbuild type to you CPACK_GENERATOR so it
would look like SET(CPACK_GENERATOR "productbuild;STGZ;TGZ")
On Wed, May 3, 2017 at 4:14 PM, Ayla Khan wrote:
> Thank you Robert. The CPACK_GENERATOR variable is currently set to
> “STGZ;TGZ”. When I
Thank you Robert. The CPACK_GENERATOR variable is currently set to “STGZ;TGZ”.
When I installed Xcode, I made sure using xcode-select that the usual command
line tools were installed. I can find productbuild in my PATH, but
CPACK_BINARY_PRODUCTBUILD is off in CPackConfig.cmake. Do I need to
Hi Ayla,
The packages that are built when executing "make package" is determined by
the variable "CPACK_GENERATOR" inside your CPackConfig.cmake ( generally
located in the root of your build directory as it is configured ).
On Fri, Apr 7, 2017 at 3:44 PM, Ayla Khan wrote:
>
Brad and I discussed this a few years ago but nothing really came of it.
Working through several find modules today, I saw many common patterns for
this and realized it should be pretty easy to implement, so here it is:
Allow the variables ENV{PackageName_ROOT} and PackageName_ROOT to be used
as
On 05/02/2017 05:47 PM, Christian Pfeiffer wrote:
> Before filtering, gcc's output gives me the libgcc and libgcc_s twice.
I think we already de-duplicate the results after extraction.
> However, I was mainly asking because the general matching logic there
> can break down in other ways, too.
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 84d0841ed7d06779b68a3950054b636f6ef4af74 (commit)
via
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 1fe2dc5ef2a1f262b125a2ba6a85f624ce150dd2 (commit)
via
03.05.2017, 11:06, "K O ranjith" :I'm using CMake for Qt creator project(in Non-Qt c++ project).In Qt kit->CMake generator I couldn't find a way to generate a Qt project (o CMakeLists.txt which can open as non-Qt project in Qt creator)(But have generator option to other IDE
I'm using CMake for Qt creator project(in Non-Qt c++ project).
In Qt kit->CMake generator I couldn't find a way to generate a Qt project
(o CMakeLists.txt which can open as non-Qt project in Qt creator)
(But have generator option to other IDE types like to Generate Visual
studio project)
Have any
13 matches
Mail list logo