Raised This Month: $ Target: $400
 0% 

vscode workspace can use relative path


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
MurbiesWalto
New Member
Join Date: Jun 2022
Old 07-15-2022 , 08:15   vscode workspace can use relative path
Reply With Quote #1

I want to make a AMX mod X script, this modules are related which game I make, so I am using workspace as configuration. Making compiler, library and output path dependent of each game. my source code has same folder as compiler

I've tried to write ./ and .\\ but it's won't work, vscode still can't find amxxpc.exe, here's my configuration workspace:

{
"folders": [
{
"path": "."
}
],
"settings": {
"amxxpawn.compiler.executablePath": "./amxxpc.exe",
"amxxpawn.compiler.includePaths": [
"./include"
],
"amxxpawn.compiler.outputPath": "../plugins",
"amxxpawn.compiler.outputType": "path"
}
}

amxxpawn.compiler.executablePath still can't figure omegle.2yu.co amxxpc.exe until I wrote full path. since this placed in same folder as source code, I also tried to remove ./ but still omeglz can't find it.

Last edited by MurbiesWalto; 08-12-2022 at 03:34.
MurbiesWalto is offline
JusTGo
Veteran Member
Join Date: Mar 2013
Location: Tunisia
Old 07-15-2022 , 10:37   Re: vscode workspace can use relative path
Reply With Quote #2

Try:

"${workspaceRoot}\\amxxpc.exe"
__________________
JusTGo is offline
fysiks
Veteran Member
Join Date: Sep 2007
Location: Flatland, USA
Old 07-16-2022 , 00:12   Re: vscode workspace can use relative path
Reply With Quote #3

Ever since I started putting my plugins on GitHub, I've actually preferred that my plugin files not be with the normal installation of AMX Mod X. At first I thought this wouldn't work when I have custom includes but I was able to resolve that because it allows you to have multiple include directories. This way, I don't have to worry about accidentally changing the default files and I can simply use a static path to my compiler. This is my config on Linux:

Code:
    "amxxpawn.compiler.executablePath": "/home/fysiks/games/amxx190/addons/amxmodx/scripting/amxxpc",
    "amxxpawn.compiler.includePaths": [
        "${fileDirname}/include",
        "/home/fysiks/games/amxx190/addons/amxmodx/scripting/include"
    ],
    "amxxpawn.compiler.reformatOutput": false,
    "amxxpawn.compiler.outputType": "path",
    "amxxpawn.compiler.outputPath": "${fileDirname}/../plugins",
    "amxxpawn.compiler.showInfoMessages": true,
As you can see, I use ${fileDirname} so that might be something you could try. I've not actually looked at the source code of the extension to see if it properly expands the compiler path but it does for includePaths and outputPath.
__________________
fysiks is offline
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 06:14.


Powered by vBulletin®
Copyright ©2000 - 2022, vBulletin Solutions, Inc.
Theme made by Freecode