FHIR Chat · Building DSTU2 · committers

Stream: committers

Topic: Building DSTU2


view this post on Zulip Jean Duteau (Oct 05 2016 at 18:51):

I've switched from using the FHIR tag that wasn't working to the dstu2-last tag. When I run the build, I get only so far before seeing the following error:
Error: Set up is not correct for the DSTU2 fork

I'm going to look into the code to see what is wrong, but I'm also asking here to see if someone can quickly what I need to do.

view this post on Zulip Jean Duteau (Oct 05 2016 at 18:53):

hmm, this is an interesting piece of code JavaGenerator.java:
if (!implDir.equals("c:\\work\\org.hl7.fhir.dstu2\\build\\implementations\\java\\"))
throw new Exception("Set up is not correct for the DSTU2 fork");

// the implementation is moved into the main trunk, but maintained from here
implDir = "c:\\work\\org.hl7.fhir\\build\\implementations\\java\\";

view this post on Zulip Jean Duteau (Oct 05 2016 at 19:03):

can someone tell me what the right tag/branch of FHIR I should use to build a STU2 version from?

view this post on Zulip Grahame Grieve (Oct 05 2016 at 19:37):

hm

view this post on Zulip Grahame Grieve (Oct 05 2016 at 19:37):

that's in all DSTU2 branches

view this post on Zulip Grahame Grieve (Oct 05 2016 at 19:38):

but I think you can take that out

view this post on Zulip Jean Duteau (Oct 05 2016 at 22:55):

I don't think you can take it out. It appears to be referring to a special directory you have on your machine where the DSTU2 files are mixed in with the rest of the reference implementation.

view this post on Zulip Jean Duteau (Oct 05 2016 at 22:55):

i'm kind of struggling here to understand how someone could take the FHIR repository and build a clean STU2 version on their machine

view this post on Zulip Lloyd McKenzie (Oct 06 2016 at 00:26):

You should only hit that code if something is wrong in your build

view this post on Zulip Jean Duteau (Oct 06 2016 at 00:27):

nope. it's special code that someone put in there that forces the implDir to be C:\work\...

view this post on Zulip Grahame Grieve (Oct 06 2016 at 00:29):

I did. I was re-organising the code base. But it would no longer be appropriate. but I can't figure out what Jean is doing. Jean, your communications mix features of 1.0.2 and 1.4.0 at random

view this post on Zulip Jean Duteau (Oct 06 2016 at 00:29):

Jean is using a build tag that Lloyd created.

view this post on Zulip Grahame Grieve (Oct 06 2016 at 00:30):

let's assume that there's no expectation that someone can build a clean STU2 version, nor any reason for them to want to

view this post on Zulip Grahame Grieve (Oct 06 2016 at 00:30):

the tag you gave me is 1.4.0 not 1.0.2

view this post on Zulip Jean Duteau (Oct 06 2016 at 00:31):

a) the code above is hit when I take a clean checkout of dstu2-latest.
b) we'll have to assume that no one will ever want to build a clean STU2 version
c) the original problem came from the tag May2016-correctedbuild

view this post on Zulip Grahame Grieve (Oct 06 2016 at 00:38):

right. I might want to do build a DSTU2 version. Maybe. But getting progressviely less likely

view this post on Zulip Grahame Grieve (Oct 06 2016 at 00:38):

the maay2016 build is 1.4.0, and not supported at all

view this post on Zulip Lloyd McKenzie (Oct 06 2016 at 00:56):

Well, using 1.4.0 resources is supported using the current build, but the old build isn't supported.


Last updated: Apr 12 2022 at 19:14 UTC