Book a Demo

Author Topic: Root Code Generation Folder  (Read 3312 times)

jnapier

  • EA Novice
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Root Code Generation Folder
« on: April 20, 2006, 05:47:06 pm »
Is there a way to specify a root code generation folder and leave out the folder from the filename of a class element?

Devs may store their project source code on different drives, different root paths, etc...  Hardcoding the full path for a filename makes it difficult for different devs to generate code to the proper place.

Hopefully I'm just missing the location where to set this property. Thanks.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Root Code Generation Folder
« Reply #1 on: April 20, 2006, 06:02:05 pm »
Can you use the relative paths from Tools / Options, or something similar?

There's been a lot of recent discussion here about how far these will get you, and how they can be used and extended. Search the forum in case this could move you forwards.
No, you can't have it!

jnapier

  • EA Novice
  • *
  • Posts: 17
  • Karma: +0/-0
    • View Profile
Re: Root Code Generation Folder
« Reply #2 on: April 20, 2006, 06:48:29 pm »
Seems like the secret to this is setting up a LocalPath.  

Settings -> Local Paths...

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Root Code Generation Folder
« Reply #3 on: April 21, 2006, 04:46:37 am »
Sorry, that's what I was thinking of. Some of the discussions were about approximating relative paths with local paths, and limitations of this. I somehow managed to confuse myself (not a difficult task) when I wrote the suggestion.

Still, search the forum over the last 60 days or so. It may save you a bit of hair-pulling when you get close to the current limitations of EA. You will also find some suggestions to Sparx that you may wish to add your voice to.
No, you can't have it!