Moving from compiling Java with GNU Make to gradle
I have a project generating many (>100) small Java tools.
For years I've used a GNU Makefile (see here) to manage the compilation of my tools (much more compact + simplier than an ant/Maven file). Basically I declared a Makefile macro that creates an executable jar using small set of parameters:
define compile-htsjdk-cmd
$(1) : ${htsjdk.jars}
$(addsuffix .java,$(addprefix ${src.dir}/,$(subst .,/,$(2))))
$(3)
(...)
${JAVAC}
-d ${tmp.dir}
-g -classpath "$$(subst $$(SPACE),:,$$(filter %.jar,$$^))"
-sourcepath ${src.dir}:${generated.dir}/java $$(filter %.java,$$^)
(...)
${JAR} cfm ${dist.dir}/$(1)$(if ${standalone},-fat).jar ${tmp.mft} -C ${tmp.dir} .
(...)
endef
$(eval $(call compile-htsjdk-cmd,referencetovcf,${jvarkit.package}.tools.misc.ReferenceToVCF,${jcommander.jar}))
$(eval $(call compile-htsjdk-cmd,sam2json,${jvarkit.package}.tools.misc.SamToJson,${jcommander.jar} ${gson.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2psl,${jvarkit.package}.tools.misc.SamToPsl,${jcommander.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2tsv,${jvarkit.package}.tools.sam2tsv.Sam2Tsv,${jcommander.jar} ))
(...)
The system worked for years without any problem.
Now, I'd like to handle more configurations (using more than one jdk, adding special things in some Manifest files ets...) And as far as I understand, gradle would be the best tool to achieve this.
I saw some examples with only one target but it's not clear to me how I could easily transform my Makefile into a gradle file. Can I put all my targets in the same build.gradle file? How can I (and should I?) mimic what I did with my makefile macro?
java gradle makefile
add a comment |
I have a project generating many (>100) small Java tools.
For years I've used a GNU Makefile (see here) to manage the compilation of my tools (much more compact + simplier than an ant/Maven file). Basically I declared a Makefile macro that creates an executable jar using small set of parameters:
define compile-htsjdk-cmd
$(1) : ${htsjdk.jars}
$(addsuffix .java,$(addprefix ${src.dir}/,$(subst .,/,$(2))))
$(3)
(...)
${JAVAC}
-d ${tmp.dir}
-g -classpath "$$(subst $$(SPACE),:,$$(filter %.jar,$$^))"
-sourcepath ${src.dir}:${generated.dir}/java $$(filter %.java,$$^)
(...)
${JAR} cfm ${dist.dir}/$(1)$(if ${standalone},-fat).jar ${tmp.mft} -C ${tmp.dir} .
(...)
endef
$(eval $(call compile-htsjdk-cmd,referencetovcf,${jvarkit.package}.tools.misc.ReferenceToVCF,${jcommander.jar}))
$(eval $(call compile-htsjdk-cmd,sam2json,${jvarkit.package}.tools.misc.SamToJson,${jcommander.jar} ${gson.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2psl,${jvarkit.package}.tools.misc.SamToPsl,${jcommander.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2tsv,${jvarkit.package}.tools.sam2tsv.Sam2Tsv,${jcommander.jar} ))
(...)
The system worked for years without any problem.
Now, I'd like to handle more configurations (using more than one jdk, adding special things in some Manifest files ets...) And as far as I understand, gradle would be the best tool to achieve this.
I saw some examples with only one target but it's not clear to me how I could easily transform my Makefile into a gradle file. Can I put all my targets in the same build.gradle file? How can I (and should I?) mimic what I did with my makefile macro?
java gradle makefile
add a comment |
I have a project generating many (>100) small Java tools.
For years I've used a GNU Makefile (see here) to manage the compilation of my tools (much more compact + simplier than an ant/Maven file). Basically I declared a Makefile macro that creates an executable jar using small set of parameters:
define compile-htsjdk-cmd
$(1) : ${htsjdk.jars}
$(addsuffix .java,$(addprefix ${src.dir}/,$(subst .,/,$(2))))
$(3)
(...)
${JAVAC}
-d ${tmp.dir}
-g -classpath "$$(subst $$(SPACE),:,$$(filter %.jar,$$^))"
-sourcepath ${src.dir}:${generated.dir}/java $$(filter %.java,$$^)
(...)
${JAR} cfm ${dist.dir}/$(1)$(if ${standalone},-fat).jar ${tmp.mft} -C ${tmp.dir} .
(...)
endef
$(eval $(call compile-htsjdk-cmd,referencetovcf,${jvarkit.package}.tools.misc.ReferenceToVCF,${jcommander.jar}))
$(eval $(call compile-htsjdk-cmd,sam2json,${jvarkit.package}.tools.misc.SamToJson,${jcommander.jar} ${gson.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2psl,${jvarkit.package}.tools.misc.SamToPsl,${jcommander.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2tsv,${jvarkit.package}.tools.sam2tsv.Sam2Tsv,${jcommander.jar} ))
(...)
The system worked for years without any problem.
Now, I'd like to handle more configurations (using more than one jdk, adding special things in some Manifest files ets...) And as far as I understand, gradle would be the best tool to achieve this.
I saw some examples with only one target but it's not clear to me how I could easily transform my Makefile into a gradle file. Can I put all my targets in the same build.gradle file? How can I (and should I?) mimic what I did with my makefile macro?
java gradle makefile
I have a project generating many (>100) small Java tools.
For years I've used a GNU Makefile (see here) to manage the compilation of my tools (much more compact + simplier than an ant/Maven file). Basically I declared a Makefile macro that creates an executable jar using small set of parameters:
define compile-htsjdk-cmd
$(1) : ${htsjdk.jars}
$(addsuffix .java,$(addprefix ${src.dir}/,$(subst .,/,$(2))))
$(3)
(...)
${JAVAC}
-d ${tmp.dir}
-g -classpath "$$(subst $$(SPACE),:,$$(filter %.jar,$$^))"
-sourcepath ${src.dir}:${generated.dir}/java $$(filter %.java,$$^)
(...)
${JAR} cfm ${dist.dir}/$(1)$(if ${standalone},-fat).jar ${tmp.mft} -C ${tmp.dir} .
(...)
endef
$(eval $(call compile-htsjdk-cmd,referencetovcf,${jvarkit.package}.tools.misc.ReferenceToVCF,${jcommander.jar}))
$(eval $(call compile-htsjdk-cmd,sam2json,${jvarkit.package}.tools.misc.SamToJson,${jcommander.jar} ${gson.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2psl,${jvarkit.package}.tools.misc.SamToPsl,${jcommander.jar} ))
$(eval $(call compile-htsjdk-cmd,sam2tsv,${jvarkit.package}.tools.sam2tsv.Sam2Tsv,${jcommander.jar} ))
(...)
The system worked for years without any problem.
Now, I'd like to handle more configurations (using more than one jdk, adding special things in some Manifest files ets...) And as far as I understand, gradle would be the best tool to achieve this.
I saw some examples with only one target but it's not clear to me how I could easily transform my Makefile into a gradle file. Can I put all my targets in the same build.gradle file? How can I (and should I?) mimic what I did with my makefile macro?
java gradle makefile
java gradle makefile
edited Jan 18 at 9:36
Pierre
asked Nov 23 '18 at 18:20
PierrePierre
23.8k2392164
23.8k2392164
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451406%2fmoving-from-compiling-java-with-gnu-make-to-gradle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53451406%2fmoving-from-compiling-java-with-gnu-make-to-gradle%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown