Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Nasser M. Abbasi" Newsgroups: comp.lang.java.programmer Subject: Re: How to develop without an IDE? Date: Sun, 22 Apr 2012 23:57:35 -0500 Organization: Aioe.org NNTP Server Lines: 57 Message-ID: References: <4f94338d$0$295$14726298@news.sunsite.dk> <4f94765c$0$284$14726298@news.sunsite.dk> <4f949830$0$295$14726298@news.sunsite.dk> Reply-To: nma@12000.org NNTP-Posting-Host: JIQ82TVrJGA8n+bUxTXA6Q.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:13812 On 4/22/2012 10:28 PM, BGB wrote: >>> >>> it does technically work though, and may make some sense, say, if one is >>> also building a bunch of C code (say, as part of a JNI wrapper for >>> native code or similar), or is generally part of a larger project for >>> which make is already used. >> >> I would rather call ant from make or make from ant to handle those >> situations. >> > > yes, this works as well. > > I guess it is probably whichever is more convenient. I found that using one good tool for everything is better than mixing things. Also, gnumake can do so many more things than just build source code. I use it to update my html files and pdf files from Latex sources, and other such things. As long as the idea that drives the tool is: Perform this action to update these prerequisites that this target depends on, then better to use one tool that does this better and for many other things, not just .java files. In my tree, I have .f, .f90, .c, .c++, .java, .tex, and many other files that I want to 'update' in my tree. Using one tool for all, is better, because one becomes better at using this one tool, and things are integrated better. gnumake+bash is pretty much all what I need. I tried ant, and found that I am doing the same thing I am already doing in my Makefile, just had to use different syntax. (I also did not like XML syntax). Also looked at Ruby script, and few other things. They all pretty much try to do what Make allready does but using different syntax. It is very easy to use gnumake to build Java and make jar files and all. Here is a link showing Makefile for Java from the best book on gnumake "Managing Projects with GNU make" by Robert Mecklenburg http://www.makelinux.net/make3/make3-CHP-9#make3-CHP-9 Chapter 9 is all about using make for build Java. As others said. If you are using an IDE with its own build system. It is better to have your own makefile to build your tree, independent of what the IDE has. This way, if you changed IDE, or move your tree somewhere else where this IDE is not available, you can still build your tree any where. --Nasser