I have seen other packages that required the rt.jar from java8 be installed in a specific directory for the build. Something like the /lib directory. I am trying to find that project to see if I can figure out what they did and how it might work for Pekko.
On Tue, May 23, 2023 at 2:09 PM Matthew Benedict de Detrich <[email protected]> wrote: > > But more to the point here, is there a Dockerfile to build the Docker > image? > > There is an in progress PR at > https://github.com/apache/incubator-pekko/pull/188 > > > Can we spell out how to configure a standard linux system to build > Pekko without the docker image? > > Not entirely sure what you mean by "standard linux system to build". > Linux's have > different distributions/package managers and most developers install things > like > OpenJDK via a package manager. While that in of itself is not problematic, > the issue > here is the "multiple installs" part (or to be more accurate you need > OpenJDK 11 > to be installed and you have to download a distribution of OpenJDK 8 to get > the > rt.jar so that Pekko can compile sources that refer to sun.misc.unsafe and > feed that > into sbt). There are other solutions like sdkman which can handle multiple > JDK > installs, but the obvious issue here is the explosion of installation > instructions ( > also this presumes that developers primary machines are Linux). > > The one big advantage that the Docker build has (aside from it just working > on any major OS) is that it uses the same docker image that github actions > does > (at least this appears to be the case from a cursory glance). > > I will try and spend some time getting > https://github.com/apache/incubator-pekko/pull/188 > finished and merged this week. > > On Tue, May 23, 2023 at 3:00 PM Claude Warren, Jr > <[email protected]> wrote: > > > > > > > Also I would like to point out/remind that even though making a source > > > package release is important > > > for Apache, it's useless for Pekko's users. It's been stated many times > > on > > > the mailing list that the people > > > actually using Pekko ultimately only care about the maven binary jars > > (i.e. > > > 1.0.0 release) and that a lot > > > of potential contributors are waiting for that 1.0.0 maven jar binary > > > release. The ironic thing here is that > > > we already have a method of creating proper artifacts, it's just done > by > > > github actions CI which doesn't > > > adhere to Apache's processes for a release and that is an example of > > what's > > > making it more complicated > > > (otherwise we could have been pushing RC's weeks/months ago). > > > > > > > > I want to point out that most of the projects I work on are libraries, > and > > as you say most users just want the binary packages. > > > > But more to the point here, is there a Dockerfile to build the Docker > > image? Can we spell out how to configure a standard linux system to > build > > Pekko without the docker image? > > > > Claude > > > > > -- > > Matthew de Detrich > > *Aiven Deutschland GmbH* > > Immanuelkirchstraße 26, 10405 Berlin > > Amtsgericht Charlottenburg, HRB 209739 B > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > *m:* +491603708037 > > *w:* aiven.io *e:* [email protected] >
