Thanks, that was exactly what I needed to know! I was compiling on OS X,
which is what caused the make confusion. After moving back to Windows,
I've got the attached, which gives me the results I'd expect and doesn't
cause any new test failures. I tried to follow the code conventions as
best I
> Yes. A few months ago I spent a few hours looking at the commands Xcode
> uses to build Swift code. For reference, here are some notes I took
> (not well organized):
>
>
> MergeSwiftModule produces .swiftmodule files,
On 12/24/2015 06:13 AM, Eric Wing wrote:
> Now that Swift is officially open source and already available for
> Linux, I started looking at the build process on Linux which I hope we
> can figure out how to incorporate into the CMake Makefile generator.
Thanks for digging in to this!
> To start
On 01/02/2016 04:11 PM, Andrey Mishchenko wrote:
> There were issues in the special-character-escaping and line-wrapping code
> which caused DragNDrop packaging to fail mysteriously at a later step with
> parsing errors in the sla.r file generated by the following code.
Thanks, applied and merged
Hi Charles,
Thanks for your efforts in exploring this topic. CMake's current language
grew incrementally out of something that was not originally intended as a
programming language. The cmState refactoring Stephen Kelly has started
is a huge step toward enabling alternative languages, but there
On 12/28/2015 07:31 AM, mikkoi wrote:
> A CMake project depends on the header only library STLSoft
> (http://www.stlsoft.org/).
> We rely on the developer having STLSoft installed or "installed"
> (pointed to by an environment variable) on his system for compilation.
Ideally packages should
On 01/07/2016 10:36 PM, Mike Fitzgerald wrote:
> I wanted to fix an issue (#13666)
Great!
> 1.) Cloned the git repo, ran bootstrap and make.
> 2.) Wrote some code in cmVisualStudio10TargetGenerator.cxx.
>
> Running make again didn't seem to recompile anything
On what platform did you build?
