Author Topic: problems with use of FILESEP and EXTENSION_EXE  (Read 1662 times)

boaz

  • Community Member
  • Posts: 43
  • Hero Points: 0
problems with use of FILESEP and EXTENSION_EXE
« on: April 19, 2012, 08:26:16 am »
Hi all,

I have a macro that is both windows/linux compatible.
I use stuff like

static _str COMMAND;
COMMAND = "bin_dir"FILESEP"executable_name"EXTENSION_EXE;

Now, all worked perfectly OK, except when I gave these macros to my co-worker which have a linux machine,
it still gave him a bad COMMAND (with '/' and 'exe').
Another weird thing is when I open the .e file on the linux SE and point the mouse to FILESEP I see the correct one!

Can anyone try to explain to me why I see windows stuff on the COMMAND str?

chrisant

  • Senior Community Member
  • Posts: 1413
  • Hero Points: 131
Re: problems with use of FILESEP and EXTENSION_EXE
« Reply #1 on: April 19, 2012, 08:47:23 am »
Does the co-worker recompile the .e file, or does the co-worker load the .ex that was compiled on Windows?

boaz

  • Community Member
  • Posts: 43
  • Hero Points: 0
Re: problems with use of FILESEP and EXTENSION_EXE
« Reply #2 on: April 19, 2012, 09:16:00 am »
hmm... I see the zip file contains my windows .ex files
I guess this is the problem...

Thanks!