We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
it's a bit clunky
the top level Makefile has targets to do ETL
the Makefile in src/ontology is a standard odk one. chr-edit.owl is not generally edited, it is mostly an importer
note: if ucsc.owl changes, chr.owl does NOT get triggered automatically. I touch chr-edit.owl to trigger this.
The text was updated successfully, but these errors were encountered:
build ontology, see #21
a887941
#21
0a6521d
Touching should not be necessary.
monochrom/src/ontology/Makefile
Line 427 in c3ca6a3
As you can see, $(COMPONENTSDIR)/ucsc.owl is a dependency of the chr-full.owl, so the goal should be retriggered whenever ucsc.owl changes.
$(COMPONENTSDIR)/ucsc.owl
Sorry, something went wrong.
We could simply trigger the odk release from the top level Makefile as well?
odk: cd src/ontology && make prepare_release
matentzn
No branches or pull requests
it's a bit clunky
the top level Makefile has targets to do ETL
the Makefile in src/ontology is a standard odk one. chr-edit.owl is not generally edited, it is mostly an importer
note: if ucsc.owl changes, chr.owl does NOT get triggered automatically. I touch chr-edit.owl to trigger this.
The text was updated successfully, but these errors were encountered: