Thanks for good information. It looks like that making Swift Foundation for
Windows would be easier than my first thought. Before reading the sources,
I imagined the full source porting from the ground up.
-Han Sangjin
2016-05-20 6:29 GMT+09:00 Tony Parker via swift-dev :
> Yes, CoreFoundation i
Hey,
Let me start by saying I just checked out the Swift repos yesterday, and
although i’ve looked at a little code and done some of the basic setup steps,
this is pretty new to me, and I could easily be doing something wrong.
Having said that, I wanted to set up Xcode so I could make a change,
Sounds like a great project. Keep us up to date with how it goes, and feel free
to ask here if you have any questions.
- Tony
> On May 20, 2016, at 1:28 AM, Sangjin Han wrote:
>
> Thanks for good information. It looks like that making Swift Foundation for
> Windows would be easier than my fi
On May 12, 2016, at 4:03 PM, John McCall via swift-dev
wrote:
>>> On May 12, 2016, at 3:21 PM, Joe Groff wrote:
On May 12, 2016, at 11:21 AM, John McCall wrote:
> On May 12, 2016, at 10:45 AM, Jordan Rose via swift-dev
> wrote:
> On May 12, 2016, at 10:44, Joe Groff w
> On May 20, 2016, at 7:56 AM, Chris Lattner wrote:
> On May 12, 2016, at 4:03 PM, John McCall via swift-dev
> wrote:
>
On May 12, 2016, at 3:21 PM, Joe Groff wrote:
> On May 12, 2016, at 11:21 AM, John McCall wrote:
>
>> On May 12, 2016, at 10:45 AM, Jordan Rose via swift-d
Foundation/NSGeometry.swift:39:25: error: value of type 'NativeType' (aka
'Double') has no member '_toBitPattern'
return Int(self.native._toBitPattern())
~^~ ~
Foundation/NSGeometry.swift:790:13: warning: result of call to
'scanUpToCharactersFromSet'
Hi Geoffrey,
Wanted to share I encountered this issue on 5/11.
(Ninja build was+is fine.)
Maybe the first 8 gyb scripts to run (I’m on a 2012 Mac Mini) are not
recognized as having finished…
As you suggest, CPU of xcodebuild, cmake, and python processes were all 0.
Regards,
Will Stanton
> On M
I ran build-script -x a few days ago. It didn't freeze, but it did take
several hours to complete (on a late-model 13" MBP).
Austin
On Fri, May 20, 2016 at 2:28 PM, Will Stanton via swift-dev <
swift-dev@swift.org> wrote:
> Hi Geoffrey,
>
> Wanted to share I encountered this issue on 5/11.
> (Ni
The failure cascade is in full effect:
lit.py: lit.cfg:881: note: Using platform module dir:
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/Ninja-ReleaseAssert/swift-linux-x86_64/lib/swift/%target-sdk-name/x86_64
-- Testing: 8207 tests, 48 threads --
Testing: 0
FAI
Hypotheses:
- There are several executables that get linked around the same time (swiftc,
swift-ide-test, sil-opt, etc), which leads to swapping.
- Building the standard library with a debug compiler is really slow.
- There’s actually a bug here somewhere, possibly due to a newer version of
CMake
10 matches
Mail list logo
