#PB_Compiler_ExecutableFile

[Little John]

In any case, when did you become the sheriff of the Feature Requests and Wishlists forum.

Why do you so often write nonsense about things that you do not understand? Go trolling somewhere else.

[User_Russian]

I propose add the constants stored path to the compiled executable. This is useful for working with files in a folder with a compiled executable.

I'm assuming that you're proposing the addition of a pre-defined target for the executable, as is normally found in other programming IDEs, where debug and release folders are implemented.

Yes.
But need constant, storing path to release executable file. Because the file is not always located in the folder with the source code.

[Little John]

Now I understand what you are after. Thank you.

[TI-994A]

Why do you so often write nonsense about things that you do not understand? Go trolling somewhere else.

Why is it important for you to understand someone else's feature request? It's a matter for the dev team; not for you to scrutinise or criticise.

I propose add the constants stored path to the compiled executable. This is useful for working with files in a folder with a compiled executable.

I'm assuming that you're proposing the addition of a pre-defined target for the executable, as is normally found in other programming IDEs, where debug and release folders are implemented.

Yes.

It seems that I understood it well enough.

It's you who are lost. As always.

[TI-994A]

Now I understand what you are after. Thank you.

Your understanding is worth squat, but you're welcome!

[Demivec]

@UserRussian: Can't you already use something like this?

Code: Select all

#releaseDirectory = "C:\folder_1\"

CompilerIf #PB_Compiler_Debugger
  ;Define configurationFiles_directory.s = #releaseDirectory ; use this like if the executible will reside in a specific directory
  
  ;Or using a directory relative to the source directory, even if the code is compiled to a temporary directory:
  ;Compiler settings// Compile/Run: Create temporary executable in the source directory
  ;Example assumes configuration files set in the parent folder of the source directory.
  Define configurationFiles_directory.s = GetCurrentDirectory() + "..\"
CompilerElse
  ;The executable file is stored in a temporary location, but it will be executed with the
  ;current path set to the directory of the source code; so loading a file from the same
  ;directory as the source code will work. 
  Define configurationFiles_directory.s = GetCurrentDirectory() + "..\" ; or = GetPathPart(ProgramFilename())
CompilerEndIf

MessageRequester("configuration directory", configurationFiles_directory)

You then would compile the executable to your release directory when you were done debugging it.

Little John wrote:
That does not make sense...

That please explain it more detailed (?), in understandable English.

But you still did not explain in detail how such a constant could help (in) solving the problem -- although I have asked repeatedly.

So how can a changing (changeable?) path be stored in the constant #PB_Compiler_ExecutableFile?
It's truly bad form to disparage the language aptitude of our international friends; especially when you are clearly no grammarian yourself, Herr LJ.

@TI-994A: It's always good to have a worthwhile description, whether in code, written language or a picture. Little John merely asked for a little clarification. English is the language of this forum (for better or for worse). Its seems your rudeness about his grammar is not conducive to our international friends.

In any case, when did you become the sheriff of the Feature Requests and Wishlists forum.

Easy there slugger, are you saying you're the sheriff in town? You sound more like someone in the peanut gallery.

You seemed to have helped discover what UserRussian was requesting but you also seem to poke everybody in the eye while doing it.

[Little John]

Why do you so often write nonsense about things that you do not understand? Go trolling somewhere else.

Why is it important for you to understand someone else's feature request?

Yes, I wanted to understand User_Russian's feature request.
I don't care whether or not you understand the reason why.
And as you have demonstrated in the past repeatedly, as serious discussion with you is not possible anyway.
Just leave me alone with your bullshit.
You'll have to look for someone else who plays with you.

[User_Russian]

#releaseDirectory = "C:\folder_1\"

On another computer, the path to source code may be other.
Need an absolute path to release executable file.

[Demivec]

#releaseDirectory = "C:\folder_1\"

On another computer, the path to source code may be other.

True.

I think you are describing that you or a group of individuals is working on separate machines to produce and debug the source code. Also you are saying that you can't share the same source code if each person's machine required a different definition (i.e. literal constant) in the code of where the files were. Are those statements correct?

The code sample I shared would still use whichever directory you decided on to hold the configuration files relative to the source code, when the program was debugging. The constant '#releaseDirectory' doesn't have to be used, I included two possibilities because I couldn't determine what you were describing.

If you compile the source to an executable (for release) the program could use GetPathPart(ProgramFilename()). If it was merely the Compile/Run option I would use GetCurrentDirectory() + "..\" because this is also based on the source code location (even if the file is compiled to a temp location).

Unfortunately I didn't see any compiler options to determine at compile-time if the program was being compiled to an executable or by using the Compile/Run option.

I still don't see an easier solution but I guess I will just have to wait for Fred or freaks' response.

Thanks for your responses.

[TI-994A]

You sound more like someone in the peanut gallery.

Pity I had to stoop to his level.

Just leave me alone with your bullshit.

Finally, something you could relate to. Enjoy!