Sorry for the late reply.
--
Egor Pugin
--
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
ber 2017 at 16:10, Raffi Enficiaud
<raffi.enfici...@mines-paris.org> wrote:
> Le 27.09.17 à 19:10, Egor Pugin a écrit :
>>>
>>> The idea is to include several "packages" (one package ~ one project in
>>> Boost) and make those available to the build, exac
quot; (or the module TEST)
> set(BOOST_LIB_${_current_package}_COMPONENTS_TEST_DEPENDENCY "test:build")
>
> --
>
> 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
urses: 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
--
Egor Pugin
--
Powered by
I see, thanks!
I'll ping when something is ready, but do not expect much in the near
future (2-4 months).
On 11 May 2017 at 16:21, Brad King <brad.k...@kitware.com> wrote:
> On 05/10/2017 10:56 AM, Egor Pugin wrote:
>> I'd like to re-use some CMake internal components, but CMa
to subdirectories, maybe choose possible public apis.
On 10 May 2017 at 19:09, Jean-Michaël Celerier
<jeanmichael.celer...@gmail.com> wrote:
>
> On Wed, May 10, 2017 at 4:56 PM, Egor Pugin <egor.pu...@gmail.com> wrote:
>>
>> but CMakeLib looks too fat.
>
>
>
> In this ag
I'd like to replace cmake language (frontend) with something different.
So, I need only target and generators.
On 10 May 2017 at 18:11, Ben Boeckel <ben.boec...@kitware.com> wrote:
> On Wed, May 10, 2017 at 17:56:07 +0300, Egor Pugin wrote:
>> I'd like to re-use some CMake inte
library (lexer, parser)
5) Commands implementation library (could be merged with 4)
True cmake power is in its generators. It's always possible to rip off
all other stuff, but in order to be tied with mainstream and
contribute back, I'm asking this.
--
Egor Pugin
--
Powered by www.kitware.com
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:
>
#L171
[2] https://github.com/cppan/cppan/blob/master/src/common/yaml.cpp#L196
On 13 January 2017 at 19:15, Brad King <brad.k...@kitware.com> wrote:
> On 01/13/2017 11:05 AM, Egor Pugin wrote:
>> Why not just use C/C++ for writing build system (bs) rules?
>>
>> CMake first will
pport: 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
>
>
s.
On 12 December 2016 at 20:02, Brad King <brad.k...@kitware.com> wrote:
> On 12/12/2016 11:35 AM, Egor Pugin wrote:
>> So, the original proposal is to make ALIAS & OBJECT targets local. And
>> explicit GLOBAL keyword will make them global again.
>
> An OBJECT libr
So, the original proposal is to make ALIAS & OBJECT targets local. And
explicit GLOBAL keyword will make them global again.
On 12 December 2016 at 18:37, Brad King <brad.k...@kitware.com> wrote:
> On 12/10/2016 04:13 PM, Egor Pugin wrote:
>> Is it possible to add GLOBAL opti
libs.
Goal as always is to not interfere with same alias names in other dirs.
A new policy may be introduced for handling new behaviour.
--
Egor Pugin
--
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
and very known projects: opencv (near
future), qt (qt-lite?, ~ end of 2016).
I'm adding small projects from time to time.
Feel free to contact me here or privately.
On 22 August 2016 at 20:52, Egor Pugin <egor.pu...@gmail.com> wrote:
> Hi Chuck,
>
>> Is this intended to run
aff R Engineer, Scientific Computing
> Kitware, Inc.
>
>
> On Sun, Aug 21, 2016 at 2:02 PM, Egor Pugin <egor.pu...@gmail.com> wrote:
>>
>> > What is the attack you want to stop? What are bad scripts and commands
>> > in this context?
>>
>> I wrote them in
onment CMake runs in.
I don't care what is around, what is in user env. This is his
responsibility. I'm just worrying for my parts of CMake stuff.
On 21 August 2016 at 20:43, Tobias Hunger <tobias.hun...@gmail.com> wrote:
> Hi Egor,
>
> Am 21.08.2016 12:34 schrieb "Egor Pugin&qu
e most cases there's no any insertions at all, so it's rare case.
On 21 August 2016 at 11:24, Tobias Hunger <tobias.hun...@gmail.com> wrote:
> Hi Egor,
>
> Am 20.08.2016 23:42 schrieb "Egor Pugin" <egor.pu...@gmail.com>:
>> You are right at many points. It
investigating possible security improvements and
this is only 'nice-to-have' feature.
On 21 August 2016 at 00:25, Tobias Hunger <tobias.hun...@gmail.com> wrote:
> Hi Egor,
>
> Am 20.08.2016 13:48 schrieb "Egor Pugin" <egor.pu...@gmail.com>:
>>
>> Hi,
&
rusted OFF
enable_command(file, On)
set_policy(enable COMMAND) # pseudo
# trusted code below
...
What do you think?
Is it possible in the latest CMake? Or can it be added in the future?
--
Egor Pugin
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
20 matches
Mail list logo
