Author Topic: Compiler Properties Upgrades  (Read 459 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1424
  • Hero Points: 111
  • Text
Compiler Properties Upgrades
« on: July 20, 2016, 09:50:07 pm »

Tools > Options > Languages > Application Languages > C/C++ > Compiler Properties


I've got several custom compilers defined.


For each I have a header file, like:

 
C:\Users\josepo03\Documents\SlickEdit\20.0.3\tagfiles\usercpp_blat.h
So, in Slick 21, even though it copied those headers to Slickedit\21.0.0\tagfiles, it didn't update these paths.
These header paths still point to the old V20 slick configuration.
The tagfile paths did get updated.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4016
  • Hero Points: 265
Re: Compiler Properties Upgrades
« Reply #1 on: July 20, 2016, 11:10:04 pm »
Right now there's no support for relative files. This would be helpful though.

jporkkahtc

  • Senior Community Member
  • Posts: 1424
  • Hero Points: 111
  • Text
Re: Compiler Properties Upgrades
« Reply #2 on: July 20, 2016, 11:16:15 pm »
Yeah, but I thought that as part of the upgrade Slick was doing a search && replace of Slickedit\<oldver>\* to Slickedit<newver>\* for many of the strings in configuration.


Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4016
  • Hero Points: 265
Re: Compiler Properties Upgrades
« Reply #3 on: July 21, 2016, 04:18:29 pm »
Please post your compilers.xml for v20. I figure it's best to test this with your compilers.xml

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 4016
  • Hero Points: 265
Re: Compiler Properties Upgrades
« Reply #4 on: July 21, 2016, 06:15:43 pm »
I've got one of your compilers.xml. New upgrade code seems to work fine with it. However, it had 20.0.1 in it when it was really from 20.0.2. Can't support that. It's a bit too random. I manually modified it to appear up-to-date (to 20.0.2) so the config upgrade would find it and change it to 21.0.0