Am 10.05.2014 23:39 schrieb waldo kitty wkitt...@windstream.net:
On 5/10/2014 5:14 PM, Sven Barth wrote:
On 10.05.2014 20:09, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to
a linux box... on windows, the project compiles fine... on linux,
On 2014-05-10 19:09, waldo kitty wrote:
box... on windows, the project compiles fine... on linux, though, all of the
files' names are lowercase but the sources have upper and CaMeL cased file
names
in the uses and include statements...
That is the normal way of doing things, and should
On 5/11/2014 3:29 AM, Sven Barth wrote:
You could add the option -vut to see which files the compiler tries to use (t)
and which it does then finally use (u). Be aware though that this might get
noisy ;)
i thought i had replied back in this thread that i had found the problem... i
used -vav
On Sat, 10 May 2014, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to a
linux box... on windows, the project compiles fine... on linux, though, all
of the files' names are lowercase but the sources have upper and CaMeL cased
file names in the
On 10.05.2014 20:09, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to
a linux box... on windows, the project compiles fine... on linux,
though, all of the files' names are lowercase but the sources have upper
and CaMeL cased file names in the uses and
On 5/10/2014 2:18 PM, Michael Van Canneyt wrote:
On Sat, 10 May 2014, waldo kitty wrote:
i surely don't want to have to edit the sources to lowercase all the uses and
includes statements every time i update my local repositories... how can i get
it to compile on linux no matter what case the
On 5/10/2014 5:14 PM, Sven Barth wrote:
On 10.05.2014 20:09, waldo kitty wrote:
i'm using git to pull a project from sourceforge to a windows box and to
a linux box... on windows, the project compiles fine... on linux,
though, all of the files' names are lowercase but the sources have upper
