On Wed, Jul 25, 2018 at 6:30 PM Jim Jagielski <j...@jagunet.com> wrote:
> As readers no doubt recall, I'm been struggling with getting > the latest HEAD of 4.2.0 to build on macOS... The various > migrations of modules from the old build to gbuild, w/o > consideration for other platforms has broken things, both > related to required libs not being linked and/or copied > (fallout from the UDK versioning changes) as well as other > issues which I can't fathom. > > Is there anyone left who knows the build process well enough > that when I run into dead-ends could provide some clues > and helpful insights on at least where to look for possible > work-arounds and fixes? > > For example, jurt builds libjpipe.dylib and the build > process correctly links that to libjpipe.jnilib. However, > during later processing, it looks like that file isn't > copied over, and the build fails saying it cannot find > libjpipe.jnilib. If I forcibly link it, I can continue > the build, but then I get: > Let's fix that jurt problem first. What does running "make showdeliverables" in the main/jurt directory give you?
