Author Topic: Slickedit on USB stick question  (Read 2161 times)

pvonkaenel

  • Senior Community Member
  • Posts: 211
  • Hero Points: 6
Slickedit on USB stick question
« on: June 30, 2009, 12:43:00 pm »
Hi all,

I have been moving my SE environment between work and home on a USB stick for quite a while now and have been very happy to have all my settings follow me around (can also take it into the lab).

However, I have recently needed to upgrade my work system to 64-bit XP and plan on sticking with 32-bit XP at home.  The unfortunate side effect of this is that the tag files are no longer portable between the 32-bit and 64-bit versions of XP - why oh why do we need a "c:\Program Files (x86)" directory in 64-bit XP?!?!?

Is there some way to have a certain system use one set of tag files, and another system use a different set, but have them share the configuration files?

Thanks,
Peter

ScottW, VP of Dev

  • Senior Community Member
  • Posts: 1471
  • Hero Points: 64
Re: Slickedit on USB stick question
« Reply #1 on: June 30, 2009, 02:53:59 pm »
Yes, this should be possible. The tag file (.vtg) for your source code is stored in the same directory as your workspace (.vpw) file. The tag files for your libraries are stored in your config directory, in a subdirectory named "tagfiles".

If I understand your goal, you want to move the same source files and configuration around but have different library tag files for the compiler libraries. Correct?

The easiest approach might be to create a tagfiles32 directory and a tagfiles64 directory and then rename the appropriate one to tagfiles when you launch SlickEdit. You could easily write a script to do the rename and then invoke "vs ...".

To create these directories, start with an empty tagfiles directory and tag your libraries on the 32-bit machine. Then copy those files to the tagfiles32 directory. Do the same thing on the 64-bit machine, but copy those tag files to the tagfiles64 directory. Those files don't need to be updated until you add/remove a library or upgrade your compiler. When that happens, copy the updated tag files back to the appropriate 32/64 directory.

I can't tell from your email if you're running SlickEdit from your USB drive or not. That works very well, and we've given out trial versions of SlickEdit preinstalled on USB drives at conventions. You can even store and use the config locally, on the USB drive, using the -sc option to tell SlickEdit where to find the config.

I have attached the autorun.inf file we use to automatically launch SlickEdit when the USB drive is inserted. There is also a vs.bat file to launch SlickEdit from the command line. The readme.txt file explains a bit about how things are set up.

Note, these were taken from a drive where both the Windows and Linux versions were installed. So, the drive contains a subdirectory for each. You may want to take the "windows" subdirectory out of the paths in those files and just have a "SlickEdit2009", or whatever you prefer to call it, directory. You can modify them to rename the tagfiles directory. Perhaps you could test for hostname and do the rename based on that.

I'd be interested in hearing if anyone else has a better suggestion for how to accomplish this.

ScottW, VP of Dev

  • Senior Community Member
  • Posts: 1471
  • Hero Points: 64
Re: Slickedit on USB stick question
« Reply #2 on: June 30, 2009, 02:55:56 pm »
Seems like only one of the attachments was included. Here are the rest...

pvonkaenel

  • Senior Community Member
  • Posts: 211
  • Hero Points: 6
Re: Slickedit on USB stick question
« Reply #3 on: June 30, 2009, 03:30:18 pm »
This seems like a good enough solution for me.

In answer to your questions, yes I have SE installed on the USB drive, and I am happily using the -sc option to pick the config out of the USB drive also.  It's really great to see software that does not muck with the Windows directory or require certain elements be put in the registry during installation.

I guess another option (besides the tagfiles32 and tagfiles64 directories) would be to add environment variable support to the tagfile sources.  This would simplify other installations for me such as the Intel compiler which provides an ICPP_COMPILER11 variable which points to the latest installed version.  I do something similar with an SDK I've written and distribute.

So instead of browsing to a source tree to use to populate a tagfile, specify an environment variable based base directory.  Is this maybe already available, but not in an obvious way?

Thanks,
Peter