adding /bin to trunk

[PhyrePhoX]

Hi,

really a small thing here, but could one of you devs please add the (empty) bin folder to the trunk? i always forget to add the folder before compiling, so compiling throws an error.
i can live without it, but with the bin folder already in trunk i could live much happier ever after

[whim]

I agree with phyrephox - especially since AFAIK just adding a dummy file
to the bin dir should do the trick ...

btw, since this is my first post after 3 months of lurking, let me add
that this is a great forum ! Kudo's & big thanks to everybody working
on / brainstorming about CHDK !

[GrAnd]

One small remark.
This folder is created normally in case of using SVN. But if you download the CHDK sources using autopacking to zip feature of assembla site, the 'bin' folder is not in the archive (ZIP does not keep empty folders in archive).

[PhyrePhoX]

hm, makes sense. i switched to svn today (not because of that) so i will not have that "problem" in the future. but maybe adding a tiny dummy file might help those who dont use svn and want to compile only occasionally. dunno, in this case they can create /bin themselves, i know. can't it be added to the makefile, that bin is created if not existing? questions, lots of questions

[GrAnd]

can't it be added to the makefile, that bin is created if not existing?

Piece of cake.
Just add into the 'firsub:' section of the topmost Makefile:

Code: [Select]

firsub: all
@echo \-\> $(PLATFORM)-$(PLATFORMSUB).FIR
[color=green]mkdir -p $(topdir)/bin[/color]


[PhyrePhoX]

works like a charm (on linux box here).
well, can this small change then be added in the trunk? not that i want to take some of your precious time

[PhyrePhoX]

revision 301:

...
+ Added autocreation of /bin directory

thanks! 

[whim]

@GrAndiose !   

I got a (somewhat) related question, why does the makefile do a

rm -f $(topdir)bin/PS.FIR     but not a

rm -f $(topdir)bin/$(PLATFORM)-$(PLATFORMSUB).FIR  ?

(can easily add it myself, but just curious)

thanks 

[GrAnd]

2whim

Because all fir-files have unique names and it is understandable which is what. The PS.FIR can confuse, because it is not clear for which camera it is.