I don’t know how these dependencies are expressed in CMake but it doesn’t seem
very difficult to do so in the autotools buildsystem, we have
AC_ARG_WITH([swift-toolchain],
[AS_HELP_STRING([--with-swift-toolchain], [Specify path to Swift toolchain])],
[swift_toolchain_path=${withval}
AC_DEFINE(HAVE_SWIFT, 1, [Define if building for Swift])
SWIFTC="$swift_toolchain_path/bin/swiftc”
in configure.ac which ends up as a SWIFTC makefile variable, so as long as that
argument is passed as an absolute path, it should work as a dependency in the
build rules
$(abs_builddir)/swift/%.o: $(abs_srcdir)/swift/%.swift
$(SWIFTC) -frontend -c $(SWIFT_ABS_SRC_FILES) -primary-file $< \
Is there a JIRA ticket for this ? the IBM folks should probably be the ones
making these changes since we still don’t have the whitelist in place for Apple
contributors to do so…
Daniel
> On Sep 23, 2016, at 13:00, Ted Kremenek <kreme...@apple.com> wrote:
>
> + Daniel
>
> Daniel: how hard would it be for the Dispatch project to be modified to add
> the swiftc binary used to build the project as a dependency?
>
>> On Sep 23, 2016, at 12:55 PM, Ted Kremenek via swift-dev
>> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
>>
>> Dispatch is a separate project. There isn’t a dependency in the Dispatch
>> project to tell it is building with a new compiler. The project would need
>> to be modified to add a dependency on the swiftc binary being used to
>> compile this project.
>>
>>> On Sep 21, 2016, at 9:39 AM, Mishal Shah via swift-dev <swift-dev@swift.org
>>> <mailto:swift-dev@swift.org>> wrote:
>>>
>>> We should look into why it's not rebuilding dependencies. Do we need to fix
>>> CMake logic? Can you please file a bug?
>>>
>>>
>>> Thanks,
>>> Mishal Shah
>>>
>>> On Sep 21, 2016, at 9:28 AM, Michael Gottesman <mgottes...@apple.com
>>> <mailto:mgottes...@apple.com>> wrote:
>>>
>>>> +CC Mishal
>>>>
>>>>> On Sep 21, 2016, at 6:59 AM, David P Grove via swift-dev
>>>>> <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
>>>>>
>>>>> I don't know how the PR jobs are setup, but the error suggests that they
>>>>> are trying to reuse too much of the workspace of previous runs.
>>>>>
>>>>> <unknown>:0: error: module file was created by an older version of the
>>>>> compiler; rebuild 'Dispatch' and try again:
>>>>> /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.o.~partial.swiftmodule
>>>>>
>>>>> --dave
>>>>>
>>>>>
>>>>> <graycol.gif>Ankit Aggarwal via swift-dev ---09/21/2016 03:08:58
>>>>> AM---This has been consistently failing on PRs, can someone look into
>>>>> this: <unknown>:0: error: module fi
>>>>>
>>>>> From: Ankit Aggarwal via swift-dev <swift-dev@swift.org
>>>>> <mailto:swift-dev@swift.org>>
>>>>> To: swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>>
>>>>> Date: 09/21/2016 03:08 AM
>>>>> Subject: [swift-dev] Swift CI PR builder dispatch linux failure
>>>>> Sent by: swift-dev-boun...@swift.org <mailto:swift-dev-boun...@swift.org>
>>>>>
>>>>>
>>>>>
>>>>> This has been consistently failing on PRs, can someone look into this:
>>>>>
>>>>> <unknown>:0: error: module file was created by an older version of the
>>>>> compiler; rebuild 'Dispatch' and try again:
>>>>> /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.o.~partial.swiftmodule
>>>>> make[2]: ***
>>>>> [/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src/swift/Dispatch.swiftmodule]
>>>>> Error 1
>>>>> make[2]: Leaving directory
>>>>> `/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src'
>>>>> make[1]: *** [all] Error 2
>>>>> make[1]: Leaving directory
>>>>> `/home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/build/buildbot_linux/libdispatch-linux-x86_64/src'
>>>>> make: *** [all-recursive] Error 1
>>>>> /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/swift/utils/build-script:
>>>>> fatal error: command terminated with a non-zero exit status 2, aborting
>>>>> /home/buildnode/jenkins/workspace/swift-package-manager-PR-Linux/swift/utils/build-script:
>>>>> fatal error: command terminated with a non-zero exit status 1, aborting
>>>>>
>>>>>
>>>>> https://ci.swift.org/job/swift-package-manager-PR-Linux/497/console
>>>>> <https://ci.swift.org/job/swift-package-manager-PR-Linux/497/console>
>>>>>
>>>>> - Ankit
>>>>> [attachment "signature.asc" deleted by David P Grove/Watson/IBM]
>>>>> _______________________________________________
>>>>> swift-dev mailing list
>>>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>>>> https://lists.swift.org/mailman/listinfo/swift-dev
>>>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> swift-dev mailing list
>>>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>>>> https://lists.swift.org/mailman/listinfo/swift-dev
>>>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>> _______________________________________________
>>> swift-dev mailing list
>>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-dev
>>> <https://lists.swift.org/mailman/listinfo/swift-dev>
>>
>> _______________________________________________
>> swift-dev mailing list
>> swift-dev@swift.org <mailto:swift-dev@swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-dev
>
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
