Date: Wed, 07 Mar 2012 00:59:31 -0300 From: Claudio André <claudioandre.br@...il.com> To: john-dev@...ts.openwall.com Subject: Re: #Include in opencl files I see no side effect. Maintainers could put files (.cl *AND* .h) where he wants. The path only have to be the same. --- It just allow you to use a #include inside the opencl file. It is related to code maintenance, you can ignore it. Claudio Em 06-03-2012 19:01, Samuele Giovanni Tonon escreveu: > On 03/06/12 21:03, Claudio André wrote: >> Hi, >> >> I noticed you guys did not use #include directive in .cl files. I used >> it, so i'm asking if: >> - it is acceptable? Necessary diff file attached. >> >> Copy (and duplicate) source code to the .cl file is not good neither. >> >> We only have to copy the .h included to the run folder (as done with .cl >> files). > what side effect could they introduce? > at the moment rather than source tree compilation i'm thinking about > distro maintainers that would like to have .cl and .h not in /etc/john > but rather in /usr/share/john/ > > Samuele
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.