Author Topic: absolute paths in project  (Read 6906 times)

aoehlke

  • Community Member
  • Posts: 48
  • Hero Points: 1
absolute paths in project
« on: February 16, 2007, 08:07:19 pm »
Is there anyway to get slickedit to stop using relative paths for includes... it seems even if I force one by typing it in, slick converts it with ../ or ./ to match the path relative to the projects home path.

Graeme

  • Senior Community Member
  • Posts: 2446
  • Hero Points: 322
Re: absolute paths in project
« Reply #1 on: February 17, 2007, 07:52:17 am »
Is there anyway to get slickedit to stop using relative paths for includes... it seems even if I force one by typing it in, slick converts it with ../ or ./ to match the path relative to the projects home path.

What O.S. and version of Slick are you using? 
What do you mean by "includes" and where do you see the relative paths?

Graeme

aoehlke

  • Community Member
  • Posts: 48
  • Hero Points: 1
Re: absolute paths in project
« Reply #2 on: February 17, 2007, 01:11:37 pm »
v11.02
solaris 9 OS

the "Directories" dialog in the project properties shows absolute paths, however, the entreis it creates in a makefile or project file, are all relative to the project file itself.

these "Directories" are used as -I includes for the compilation.

Graeme

  • Senior Community Member
  • Posts: 2446
  • Hero Points: 322
Re: absolute paths in project
« Reply #3 on: February 17, 2007, 11:21:41 pm »
On Windows, I'm getting absolute paths in the project (.vpj) file.

For me, the working directory is shown as relative, and stored in the project file as relative.  In project.e, the doOK() function calls okDirectories() which converts to a relative path - by calling the "relative" function.  I see no sign that the include paths are stored as relative, regardless of the O.S. / platform.  The function _ProjectSet_IncludesList does no conversion and I don't see any conversion in project.e where _ProjectSet_IncludesList is called.  Maybe it's different on your system.

In _parse_project_command, you can see %IR and %IN can be used for converting absolute to relative (%IR) and relative to absolute (%IN) which they do by calling _relative_includedirs and _absolute_includedirs respectively.

Graeme


aoehlke

  • Community Member
  • Posts: 48
  • Hero Points: 1
Re: absolute paths in project
« Reply #4 on: February 18, 2007, 02:05:21 pm »
anyone help on solaris?

aoehlke

  • Community Member
  • Posts: 48
  • Hero Points: 1
Re: absolute paths in project
« Reply #5 on: February 20, 2007, 07:35:35 pm »
From slickedit support:

Aaron,

Unless the path to the source/include files are on different drive, SlickEdit will attempt to convert the absolute path to one relative to the project file.  I will log this in our Feature Request Tracker and we can hope to see this implemented in a future release.

Regards
« Last Edit: February 20, 2007, 10:07:14 pm by aoehlke »

Graeme

  • Senior Community Member
  • Posts: 2446
  • Hero Points: 322
Re: absolute paths in project
« Reply #6 on: February 20, 2007, 09:18:05 pm »
Hmm.  Well I have a project that's on the same drive as the include files and I'm getting absolute paths in the project file for the includes.

Graeme

aoehlke

  • Community Member
  • Posts: 48
  • Hero Points: 1
Re: absolute paths in project
« Reply #7 on: February 20, 2007, 10:02:31 pm »
are u on solaris?

Graeme

  • Senior Community Member
  • Posts: 2446
  • Hero Points: 322
Re: absolute paths in project
« Reply #8 on: February 20, 2007, 10:31:16 pm »
are u on solaris?

Nope, Windows, but I can't imagine why Solaris would be any different.  Must be something I'm missing.

Graeme