Author Topic: Include-Directory redirection: Another good reason for using the CSED-Editor  (Read 2353 times)

0 Members and 1 Guest are viewing this topic.

Offline Theo Gottwald

  • Administrator
  • Hero Member
  • *****
  • Posts: 966
    • it-berater
I just had that case. An "old" PB 9 Programm.
I could have just been compiling it for PB, but i wanted some of the new features.

Soon i realized, that it would mean quite some changes because ir needed other include files and ".inc" libraries.

So i started CSED and used the

Code: [Select]
$CSED_INCPATH = "D:\01_PB\02_Resources\05-Lib-A\;D:\01_PB\PBWin10\WINAPI_II\"
directive and this way i could just compile it using Jose's include files, without changin any settings in the editor itself.

I like this advantage of CSED to be able to redirect the include directoris using the source-code.
Because i do not need to change anything in the editor settings.

Having said that, let me add that Jose's include files arenot only much larger then the original includes, but also very compatible to PB 9. This way i could campile the old code without further changes using PB 10.
« Last Edit: July 12, 2011, 10:10:48 PM by Theo Gottwald »