fdorg / flashdevelop

FlashDevelop is a free and open source code editor.
MIT License
818 stars 219 forks source link

haxelib reference bug #1257

Open loudoweb opened 8 years ago

loudoweb commented 8 years ago

I have set a default version for openfl of 3.6.1 (with haxelib command). In a project I need an other version so I have set in my project.xml (openfl file) : <haxelib name="openfl" version="3.1.0"/>

In Project window in FlashDevelop, I have the two libraries instead of the one I defined for this project (3.1.0): Project window

Gama11 commented 8 years ago

This could well be a Lime / OpenFL bug, FlashDevelop just displays what Lime's display command returns.

Could you check what the release.hxml / debug.hxml files in your export folder look like? (export/<target>/haxe) - do they contain -cp openfl twice?

loudoweb commented 8 years ago

No it doesn't contain twice -cp openfl. I have only the one I defined in project.xml.

IBwWG commented 7 years ago

I'm having the same thing with the flixel version. In my case it does appear twice in release.hxml and debug.hxml: once with 4.0.0 and once with git. I think it's because I also use flxscrollablearea, which depends on 4.0.0, even though my project.xml does not specify a version and haxelib list gives git for the current flixel version (which is what I want.)

But I wasn't having this trouble last month...what changed? I installed a new version of flixel for another project, and when I was done, set the flixel version back to git. That doesn't appear to be the correct way to do it, I guess?

flxscrollablearea, for its part, doesn't have anything too wacky in its json:

"dependencies": {
    "flixel": "4.0.0",
    "openfl": "3.6.0"
  }

I have openfl 3.6.1 installed and set to, and that doesn't cause a duplication...

I can even shut down haxedevelop, manually delete the 4.0.0 references from my .hxproj file, and upon launch they get added back in and showing a double reference.

I don't care so much about the double reference, except that now my project won't compile, because things that are only present in the git version of flixel aren't in 4.0.0 and it somehow is only looking in 4.0.0. Not if I press F4, though, then it finds it. But the compiler doesn't.

IBwWG commented 7 years ago

Maybe since my .hxml files do contain two -cp flixel lines, that makes what I'm talking about a lime issue, separate from loudoweb's issue? In that case I guess I should open a new issue over there. Sorry for the hijack.