Book a Demo

Author Topic: Relative file path when adding files to a package?  (Read 3289 times)

TheProgrammer

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Relative file path when adding files to a package?
« on: June 30, 2008, 07:48:06 pm »
When adding a local file to a package (Package context menu->Properties->Files tab) is there any way to specify the path relative to the current project? I'm only able add an absolute path to the file : this won't work as the project is shared between several engineers with differing directory trees. The file path field also doesn't seem to accept any macros, i.e. the repository path macro. Is there any way to get around this problem?

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Relative file path when adding files to a pack
« Reply #1 on: June 30, 2008, 10:47:50 pm »
Check out local paths in EA help. I think this will get you to where you want to be, or close in any case.
No, you can't have it!

TheProgrammer

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Relative file path when adding files to a pack
« Reply #2 on: July 01, 2008, 12:43:47 am »
Thanks for the reply. Unfortunately the local path macros don't seem to work in the file path field. Either I'm missing something or this is a bug.

Frank Horn

  • EA User
  • **
  • Posts: 535
  • Karma: +1/-0
    • View Profile
Re: Relative file path when adding files to a pack
« Reply #3 on: July 01, 2008, 03:56:22 am »
Not a bug in the strict sense of the word, but a big gap for sure. It would strikingly break the EA philosophy of deployment to local machines cause it would make files attached to packages useless in a distributed environment.