add libdispatch to linux buildbot / development snapshots


(Dave Grove) #1

Hi,

  After libdispatch PR#49 gets merged, it would be feasible to start
including libdispatch in the linux buildbot presets and thus (I think) in
the development snapshots as well.

  The additional libdispatch pre-reqs (libblocksruntime-dev
libkqueue-dev systemtap-sdt-dev autoconf libtool) would need to be
installed on the build machines.

  Because libpwq is being included as a gitsubmodule, there are extra
steps after cloning swift-corelibs-libdispatch (git submodule init; git
submodule update) that the automated build would need to do.

  Is there anything I can do to help move this along? Anything I've
overlooked?

thanks,

--dave


(Tony Parker) #2

Hi Dave,

Let me talk to a few people offline and get back to you on this. We should be able to get it setup correctly.

- Tony

···

On Feb 12, 2016, at 7:56 AM, David P Grove via swift-corelibs-dev <swift-corelibs-dev@swift.org> wrote:

Hi,

After libdispatch PR#49 gets merged, it would be feasible to start including libdispatch in the linux buildbot presets and thus (I think) in the development snapshots as well.

The additional libdispatch pre-reqs (libblocksruntime-dev libkqueue-dev systemtap-sdt-dev autoconf libtool) would need to be installed on the build machines.

Because libpwq is being included as a gitsubmodule, there are extra steps after cloning swift-corelibs-libdispatch (git submodule init; git submodule update) that the automated build would need to do.

Is there anything I can do to help move this along? Anything I've overlooked?

thanks,

--dave

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev


(Dmitri Gribenko) #3

I think we need to move libpwq to the primary repository or the Apple
org first. Otherwise our CI won't be able to tag builds, people won't
be able to reproduce builds etc.

Dmitri

···

On Fri, Feb 12, 2016 at 7:56 AM, David P Grove via swift-corelibs-dev <swift-corelibs-dev@swift.org> wrote:

Hi,

After libdispatch PR#49 gets merged, it would be feasible to start including
libdispatch in the linux buildbot presets and thus (I think) in the
development snapshots as well.

The additional libdispatch pre-reqs (libblocksruntime-dev libkqueue-dev
systemtap-sdt-dev autoconf libtool) would need to be installed on the build
machines.

Because libpwq is being included as a gitsubmodule, there are extra steps
after cloning swift-corelibs-libdispatch (git submodule init; git submodule
update) that the automated build would need to do.

Is there anything I can do to help move this along? Anything I've
overlooked?

--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/


(Dave Grove) #4

ok. I have a 3 line hack/patch to libpwq's Makefile.am in my fork to
change its installation behavior it didn't make sense to push upstream.
I'll see if I can come up with a better way to get the same effect that
could be pushed upstream. Otherwise, everything else we have fixed has
already been merged upstream.

--dave

···

Dmitri Gribenko <gribozavr@gmail.com> wrote on 02/12/2016 11:44:13 AM:

I think we need to move libpwq to the primary repository or the Apple
org first. Otherwise our CI won't be able to tag builds, people won't
be able to reproduce builds etc.