search

vshaxe / hxcpp-debugger

Visual Studio Code Debugger for Haxe/HXCPP applications
MIT License
26 stars 12 forks source link

Type not found : hxcpp.debug.jsonrpc.Macro #20

Open Necdilzor opened 5 years ago

Necdilzor commented 5 years ago

Hello there, I'm trying to use this extension to debug Windows builds of HaxeFlixel games.

Whenever I try to install this extension to debug my applications I get this error: Type not found : hxcpp.debug.jsonrpc.Macro And as such, I can't even build my application now.

I'm using Haxe 4.0.0-rc.3 (although the same happened with 4.0.0-rc.2) and HaxeFlixel 4.6.2. I also added <haxelib name="hxcpp-debug-server" /> to my Project.xml file.

Build command used: lime build windows -debug --haxelib=hxcpp-debug-server --connect 6000

I found out that the missing file Macro.hx is inside the vscode extension folder at hxcpp-debugger\hxcpp-debug-server\hxcpp\debug\jsonrpc\Macro.hx. At the same time, my Haxe installation folder has only a .dev file at haxe\lib\hxcpp-debug-server. Is this normal?

The content of the .dev file is:

c:\Users\Agustín\.vscode\extensions\hxcpp-debugger\hxcpp-debug-server

Maybe the í in c:\Users\Agustín\ is causing trouble?

What could be wrong here?

Thanks for your time.

Gama11 commented 5 years ago

Hm.. unless you built the debugger from source, c:\Users\Agustín\.vscode\extensions\hxcpp-debugger\hxcpp-debug-server doesn't seem like the correct path. It should end in something like ...\.vscode\extensions\vshaxe.hxcpp-debugger-1.2.4\hxcpp-debug-server.

Necdilzor commented 5 years ago

I tried moving the extension from c:\Users\Agustín\.vscode\extensions\hxcpp-debugger\hxcpp-debug-server to D:\GameProjects\haxeflixel\hxcpp-debugger\hxcpp-debug-server and updated the .dev file. Now it builds and works. So I guess the issue is that the .dev file can't have characters like í on its path to hxcpp-debug-server.

Yeah, I tried building the extension from source as the normal extension install had the same problem.

Gama11 commented 5 years ago

Hm, I see. Maybe we should publish the library to Haxelib as well to make it easier to work around it, but that still doesn't really solve the problem...