Hi and questions!

[marksibly]

Hi,

I'm a new CodeLite user and so far I'm very impressed!

A few things though:

* To make a 'dll' on the Mac, I had to change 'g++ -shared' to 'g++ -dynamiclib' (somewhere - it seems to have stuck 'globally' though).

* When importing an MSVC sln on the Mac, I end up with lots of backslahes at the front of filenames, eg: '.\file1.cpp', '..\..\file2.cpp' etc. CodeLite can't then open/compile these files.

* It keeps bugging me at startup to 'Create Symbols Database'! What dir should I select on Mac to make it happy, or how can I turn it off?

Now some questions:

What's the difference between workspace config and project config?

I want to setup a multiplatform (macos/win32/linux) workspace with at least 2 configs (debug/release). The workspace consists of a combination of static lib, dll, exe etc projects.

I assume this has something to do with workspace vs project configs etc, but I'm not quite sure how workspace config affects project config and vice versa.

What would people recommend here?

Any hints most welcome!

Bye,
Mark

[marksibly]

Hi,

Ok, after a little poking around I think I've got the general idea: A workspace config is just a set of 'active' project configs?

So, changing workspace config just changes currently active project configs - does changing workspace config affect anything else?

[eranif]

Ok, after a little poking around I think I've got the general idea: A workspace config is just a set of 'active' project configs?

Correct

So, changing workspace config just changes currently active project configs - does changing workspace config affect anything else?

No

To make a 'dll' on the Mac, I had to change 'g++ -shared' to 'g++ -dynamiclib' (somewhere - it seems to have stuck 'globally' though).

go to 'settings -> build settings...' select the 'gnu g++' tab.
Switch to 'Tools' and replace 'g++ -shared' with 'g++ -dynamiclib' - this will affect globaly (I suggest you do the same for 'gnu gcc')

When importing an MSVC sln on the Mac, I end up with lots of backslahes at the front of filenames, eg: '.\file1.cpp', '..\..\file2.cpp' etc. CodeLite can't then open/compile these files.

- There is a small script I wrote http://codelite.svn.sourceforge.net/vie ... vision=937 download it (give it execution permissions)
- cd to the workspace directory
- and simply run: ./le_dos2unix.sh

this will convert all \ into / and .dll to .so on all .workspace/.project that it will find - it is part of the distribution for Linux, but it looks like I should make it part of the bundle as well.

It keeps bugging me at startup to 'Create Symbols Database'! What dir should I select on Mac to make it happy, or how can I turn it off?

select /usr/include/c++/4.x/ this will create tags for the entire STL (you will get code completion for std:: namespace and more)
Another option:
If for example, you are using 3rd party library, you may do this to get code completion for it:
- switch to the explorer tab (in the 'Workspace View' pane)
- locate the directory where the library is placed
- right click on it and select 'Add Tags...'
- The wizard will start, already pointing to that directory, tick the directories where your files are located and click 'Finish'

You may repeat this step as much as you need and by selecting the same database name, all tags are gathered in the same database.

I also suggest you read this:
http://codelite.org/LiteEditor/CodeCompletion
http://codelite.org/LiteEditor/ConfigurationManager

Nice to hear from a Mac user, and I am looking forward for feedback
Eran

[marksibly]

Thanks, all going well now.

I am really enjoying codelite - it's a bit like code blocks, but much cleaner/simplified and doesn't crash on the Mac every 5 mins!

A quick suggestion:

I've always felt it'd be kind of nice to have a 'disable' option for files - for example, sometimes you don't want a file to be compiled, but it's still nice to have it around in the explorer view for reference. This is often the case if your refactoring some stuff around and creating new files.

Perhaps this could be done 'per config', so the file 'right click' menu has an addition 'enable' submenu with a list of configs in it, each ticked if file is enabled for that config. If a file is not enabled for current config, it's 'greyed out'. This also addresses the issue of platform specific files I guess. Another approach would be to implement a file->settings panel.

Also...if a file is disabled for all configs, perhaps an svn delete option could be added to the svn info page (which is very cool!).

Just some thoughts...

Bye!
Mark

[eranif]

Also...if a file is disabled for all configs, perhaps an svn delete option could be added to the svn info page (which is very cool!).

More SVN options are available from the 'Explorer' tab

Eran