How do you deal with the library settings when you have a release and a development version of a component? Do you change the library settings all the time depending on whether you're working on the dev version or you're using the released one?
David Heffernan Lately I've been fiddling the Lazarus IDE, I might be wrong - it seems only allow setting library paths for projects, but no global library path settings... Seems to be a good practice.
Thanks guys. What I meant is which directories you have in the IDE. For example, say I develop MyComponent and I have a release version. In an app I develop I add the MyComponentRelease Folder in the library. Then, I want to work on another version of MyComponent. This means I need the MyComponentDevelopment Folder in the library settings. Do I do these changes all the time?
I'm suggesting that you don't use global library path at all. As for project library paths, I don't use them. I just include the source files I need in my project. But a project library path is perhaps reasonable, even if I don't like them.
David Heffernan Lately I've been fiddling the Lazarus IDE, I might be wrong - it seems only allow setting library paths for projects, but no global library path settings... Seems to be a good practice.
ReplyDeleteThanks guys. What I meant is which directories you have in the IDE. For example, say I develop MyComponent and I have a release version. In an app I develop I add the MyComponentRelease Folder in the library. Then, I want to work on another version of MyComponent. This means I need the MyComponentDevelopment Folder in the library settings. Do I do these changes all the time?
ReplyDeleteI'm suggesting that you don't use global library path at all. As for project library paths, I don't use them. I just include the source files I need in my project. But a project library path is perhaps reasonable, even if I don't like them.
ReplyDelete