dirty file/project settings detection?

[Thund]

Sorry for my interruption. I was about to create a new topic talking about my problems when trying to set the Working Directory and I found that you were already talking about that. I'm on Mac OS X (Mountain Lion 10.8.5) using lldb. The problem is simple: it does not matter what I write in the Working Directory field of the Project Settings window (General section), it always sets it to the project's directory (I know that by calling getcwd). I need this to work because my applications search for some configuration files at the same directory they are, when debugging. Have you tested on this OS? Thanks in advance.

PD: If you prefer, I can create the new topic.

[eranif]

The problem is simple: it does not matter what I write in the Working Directory field of the Project Settings window (General section), it always sets it to the project's directory (I know that by calling getcwd)

This is already fixed in git head.
You can compile a new codelite from sources, or its super important - PM me and I will build you a new codelite for OSX

Eran

[petah]

AFAIK that problem has been fixed a few days back, did you try building CL trunk?

The remaining issue has moved to build files being overwritten by different workspaces if they share source files.

cheers,

-- p

[Thund]

The problem is simple: it does not matter what I write in the Working Directory field of the Project Settings window (General section), it always sets it to the project's directory (I know that by calling getcwd)

This is already fixed in git head.
You can compile a new codelite from sources, or its super important - PM me and I will build you a new codelite for OSX

Eran

AFAIK that problem has been fixed a few days back, did you try building CL trunk?

The remaining issue has moved to build files being overwritten by different workspaces if they share source files.

cheers,

Thanks both for your quick answers.