Absolute paths in .kdev4/ dir

[Aleix Pol]

On Sun, Jul 11, 2010 at 2:02 PM, Valentin Pavlyuchenko
<thevalik at gmail.com>wrote:

> I want to fix absolute CMake paths in .kdev4/<projname>.kdev4
> It now causes problems when moving project to the different path.
>
> The idea is to use relative paths. I think it's better to store
> relative paths in the new variables near to old absolute paths for
> compatibility of new projects with older KDevelop4 versions (4.0).
> Automatic old project file conversion on open is also required.
>
> Example:
>
> Old project .kdev4/test.kdev4 (project is stored in
> /home/valentine/projects/test):
>
> [Buildset]
>
> BuildItems=@Variant(\x00\x00\x00\t\x00\x00\x00\x00\x01\x00\x00\x00\x0b\x00\x00\x00\x00\x01\x00\x00\x00\x08\x00t\x00e\x00s\x00t)
>
> [CMake]
> BuildDirs[$e]=/home/valentine/projects/test/build
> CMakeDir=/usr/share/cmake-2.8/Modules
> Current CMake Binary=file:///usr/bin/cmake
> CurrentBuildDir=/home/valentine/projects/test/build
> CurrentBuildType=Release
> CurrentInstallDir=file:///usr/local
> Extra Arguments=
> ProjectRootRelative=./
>
> [MakeBuilder]
> Number Of Jobs=1
>
>
> Proposition for new format:
>
> [Buildset]
>
> BuildItems=@Variant(\x00\x00\x00\t\x00\x00\x00\x00\x01\x00\x00\x00\x0b\x00\x00\x00\x00\x01\x00\x00\x00\x08\x00t\x00e\x00s\x00t)
>
> [CMake]
> BuildDirs[$e]=/home/valentine/projects/test/build
> BuildDirsRelative[$e]=build
> CMakeDir=/usr/share/cmake-2.8/Modules
> Current CMake Binary=file:///usr/bin/cmake
> CurrentBuildDir=/home/valentine/projects/test/build
> CurrentBuildDirRelative=build
> CurrentBuildType=Release
> CurrentInstallDir=file:///usr/local
> Extra Arguments=
> ProjectRootRelative=./
>
> [MakeBuilder]
> Number Of Jobs=1
>
>
> This gives compatibility with older versions. New KDevelop should read
> BuildDirsRelative instead of BuildDirs and CurrentBuildDirRelative
> instead of CurrentBuildDir.
>
> --
> Best regards,
> Valentin Pavlyuchenko
>
>
>
> 2010/7/10 Aleix Pol <aleixpol at kde.org>:
> > let's rephrase.
> > what do you want to fix?
> >
> > On Sat, Jul 10, 2010 at 1:30 PM, Milian Wolff <mail at milianw.de> wrote:
> >>
> >> On Saturday 10 July 2010 13:12:05 Aleix Pol wrote:
> >> > What do you want to fix with that?
> >> > To me it makes perfect sense to have the relative source path,
> actually
> >> > I
> >> > think this should move to the project file and with absolute project
> >> > files
> >> > that's not possible.
> >>
> >> exactly, but currently only absolute paths are stored :)
> >> --
> >> Milian Wolff
> >> mail at milianw.de
> >> http://milianw.de
> >>
> >> --
> >> KDevelop-devel mailing list
> >> KDevelop-devel at kdevelop.org
> >> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> >>
> >
> >
> > --
> > KDevelop-devel mailing list
> > KDevelop-devel at kdevelop.org
> > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> >
> >
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>

I think that using relative paths might be not the best solution.
If the project was moved then we can remove the current configuration and
ask for it again. Relative paths sound workaround-ish to me.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100711/1f7231c4/attachment.html>