Hi, If the make procedure uses the filenames as targets or dependencies in Make, you'll have a heck of a time working with white spaces in the filenames since this is the default delimiter and there is no official escape character. I've used macros to define space characters, but it's clumsy and not applicable for all situations.
If the 'find' is just in a command definition, then the '-print0' option is an easy fix. Scott On Feb 8, 2015, at 10:19, Oliver Welter <[email protected]> wrote: > Hi Sergei > > Am 08.02.2015 um 00:25 schrieb Sergei Vyshenski: > >> My make procedure breaks because of files with space in a name, like >> >> CA Operator.yaml >> RA Operator.yaml >> >> More definitely, output of "find" presents such a file as two >> (non-existent) files. >> >> Is it that necessary to have those spaces? > > The names correlate to the internal role names and they have spaces for > historical reasons. Besides, spaces in names should not throw a problem > nowadays. > > Might it be possible to use another seperator in your make script. The > find programm will use the NUL character when you add "-print0", of > course you also need to change the sep. at the target script. > > Oliver > > -- > Protect your environment - close windows and adopt a penguin! >
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
