Hi,
There are many use of the macro DEPLOYMENT_TARGET_WINDOWS and Win32
functions in the directory
swift-corelibs-foundation/tree/master/CoreFoundation.
Could someone tell me about who tried to porting or ported or any history?
-Han Sangjin
___
swift-d
> On May 18, 2016, at 11:13 AM, Jordan Rose via swift-dev
> wrote:
>
> Hi, fellow Mac users. On GitHub, commit hashes are autolinked (within
> repositories, anyway), but that doesn't apply to mail clients, or, um,
> external bug tracking clients *cough*Radar*cough*. I've found myself wanting
On Wednesday, May 18, 2016, Joe Groff wrote:
>
> > On May 18, 2016, at 1:51 PM, Saleem Abdulrasool via swift-dev <
> swift-dev@swift.org > wrote:
> >
> > Hi,
> >
> > It seems that there are assumptions about the ability to create relative
> address across sections which doesn't seem possible on W
Should be fixed by e248f83df9afc7bd588f264984f6ca0396c8015d.
-Joe
> On May 18, 2016, at 4:00 PM, Joe Groff via swift-dev
> wrote:
>
> Looks like my fault. I'll look into fixing it.
>
> -Joe
>
>> On May 18, 2016, at 3:58 PM, no-re...@swift.org wrote:
>>
>> New issue found!
>>
>> [FAILURE] o
Looks like my fault. I'll look into fixing it.
-Joe
> On May 18, 2016, at 3:58 PM, no-re...@swift.org wrote:
>
> New issue found!
>
> [FAILURE] oss-swift-incremental-RA-osx [#4118]
>
> Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/4118/
> Project: oss-swift-increment
> On May 18, 2016, at 1:51 PM, Saleem Abdulrasool via swift-dev
> wrote:
>
> Hi,
>
> It seems that there are assumptions about the ability to create relative
> address across sections which doesn't seem possible on Windows ARM.
>
> Consider the following swift code:
>
> final class _Contigu
Hi,
It seems that there are assumptions about the ability to create relative
address across sections which doesn't seem possible on Windows ARM.
Consider the following swift code:
final class _ContiguousArrayStorage { }
When compiled for Windows x86 (via swiftc -c -target i686-windows
-parse-as
> On May 18, 2016, at 11:13 AM, Jordan Rose via swift-dev
> wrote:
>
> Hi, fellow Mac users. On GitHub, commit hashes are autolinked (within
> repositories, anyway), but that doesn't apply to mail clients, or, um,
> external bug tracking clients *cough*Radar*cough*. I've found myself wanting
Actually, on closer look I’d like to do it the other way around and clean up my
changes and integrate the python script in to the build script for OSX.
The reason is that it produces a dylib, which is easier to install in an
xctoolchain. I tried putting the .framework in the toolchain’s
/System
Great, thanks. IMHO it would be nice to open a bug on Foundation/SwiftPM/XCTet
when changes like this go in just so we know of the intentional change we need
to react to, it is sometimes hard to keep up with the language changes without
notification.
- Daniel
> On May 17, 2016, at 9:25 PM, Ch
Yeah it all makes much more sense now. I was so stuck in the terminal I
completely forgot there even was an Xcode project.
So I’ll submit a patch making the python script farm out to xcodebuild instead
of trying to configure a Mac.
> On 18 May 2016, at 16:35, Philippe Hausler wrote:
>
> Yea,
Yea, the python build scripts only work on Linux. Before the initial drop I was
tinkering with making it build both but the Xcode project was just simpler and
easier to maintain. Either use xcodebuild or use the Xcode IDE instead of the
ninja builders.
It might be nice one day to unify the Linu
To clarify: xctest tries to build Foundation using xcodebuild. Actually, I
wonder why it didn’t use xcodebuild the first time.
Maybe it should. Maybe that’s the way out of this.
> On 18 May 2016, at 16:21, Karl wrote:
>
> OSX 10.11.4, latest Xcode and SDKs.
>
> The Swift compiler is correct
OSX 10.11.4, latest Xcode and SDKs.
The Swift compiler is correct here - the CF header has an availability
attribute, but the Foundation symbol doesn’t. Either the Foundation symbol
needs to become less available, or the CF one needs to become more available.
I bypassed it by removing the restr
I’m trying to fix Foundation on OSX (or am I doing something wrong? I was
surprised to find it didn’t build)
I’ve run in to a problem, though: swift is telling me that certain APIs are not
available:
> Foundation/NSNumberFormatter.swift:19:70: error: 'ordinalStyle' is only
> available on OS X
15 matches
Mail list logo
