2013/10/25 Javier Fileiv > > 2013/10/25 Michael Olbrich > >> On Thu, Oct 24, 2013 at 11:51:47AM +0200, Javier Fileiv wrote: >> > 2013/10/24 Michael Olbrich >> > >> > > On Wed, Oct 23, 2013 at 09:52:05AM +0200, Javier Fileiv wrote: >> > > > 2013/10/23 Marc Kleine-Budde >> > > > > On 10/22/2013 03:44 PM, Javier Fileiv wrote: >> > > > > > Hello everyone, I have the following scenario. >> > > > > > >> > > > > > My package is in a folder, where there is another folder inside >> which >> > > > > > contains the Makefile. No autotools is required. >> > > > > > >> > > > > > If I create a newpackge with ptxdist newpackage target, it will >> > > create >> > > > > > the .make and .rule file. But how can I tell to the "compile" >> step >> > > that >> > > > > > my Makefile is in ./src an not in ./ ?? I was trying to add a >> simple >> > > > > >> > > > > define in your .make file >> > > > > >> > > > > _SUBDIR := src >> > > > > >> > > > > >> > > > Am I able to add my own bash scripts there? >> > > >> > > I don't understand this. >> > >> > >> > What I meant with that is if I can add my bash instruction on every >> section >> > to be executed.For example if I call 'ptxdist prepare MY_PACKAGE' and I >> > write 'echo "MY OWN PREPARE STRING" ' in the .make file, it will write >> out >> > "MY OWN PREPARE STRING" on the console output. >> > >> > Did you get what I try to say? Sorry.. it's my mistake if not. >> >> The stages are just make targets. You can do anything you want there. >> Take a look at e.g. rules/python.make in ptxdist. It does some extra stuff >> before calling world/prepare (which then runs configure). >> >> Michael >> >> I will !! Thank you very much! > Now I see that they add '@' at the beginning of the line!