frozenflash!

It's ok, i don't mind dealing with the error when creating a new project, it's just a click on the error panel. I prefer much more to have the swcsettings in the obj folder because If I have 5 or 10 projects in the rook the swcsettings would make a mess.

With the version you uploaded i don't have to think about anything but were I want the output to go to so it's almost perfect. It would be great if the official release used the obj folder but I suppose there must be a reason not to.

I'm VERY happy with the fast response that the posts get in the FD forums. It's pretty incredible.

You guys are awesome.

SP.

Hi,
I think these files should be in the root folder because they are also project files like .as3project. The config files in the obj folder will be recreated everytime you compile your project. But the SWC project files get only created once. So if you delete them, your swc project is gone whereas deleting the obj folder doesn't have any consequences.

Just my opinion. I don't care where the project files are located.

frozenflash

You're right deleting the files makes you lose the config. I agree, in the root it's ok then.

Hope FD gets an official export swc utility so the settings get saved with the rest of the stuff.

Warappa, can the latest version compiled and posted in the download at sourceforge?

Thanks guys!

Done.

Added context menu integration for as3 project files: ExportSWC 2.2

This is sweet! I've been using it all day to compile some levels into a game. Great time saver, I used to go in, compile and then back out the main project, now it's compiled in an instant.

Hi, congratulations on a much needed plugin that allows for proper project design.

I'm having some problems compiling and I'm posting my question here before I go tinkering around with the plugin source. I use the mx.* classes in my project (a SWC), StringUtil to be specific. Until recently, I had no problem compiling. FlashDevelop recognized the classes (code-completion-wise) and the flex compiler was happy.

Then I added a reference to several as3commons SWC's and refactored parts of my code. At some point during this process I noticed that FD stopped giving me highlighting and code completion for the mx classes. Ever since, when I try to compile I get "Error: Definition mx.utils:StringUtil could not be found". At first this affected normal SWF build as well, but after some snooping around the forums I found a suggestion to add "Library\AS3\frameworks\Flex3" to the compiler options under "Intrinsic libraries". This did the trick for highlighting + normal SWF build, even though it seems weird this suddenly became necessary when it was working fine before. For the SWC however, it didn't help.

Regarding the first problem - mx.* classes stop being recognized - I'm sure it's some FD setting that got borked somehow (even though I sifted through my project SVN history and found no change to any of the XML config files that could have caused this). In any case, ExportSWC was obviously affected by this, but if I can fix the main FD problem, it'll probably fix it too.

The second problem, however - and one that probably should be treated as a plugin bug - is that I can't get ExportSWC to recognize the necessary compiler option. When I look in the obj directory, I see that while is added to the *Config.xml file, it isn't added to the *.flex.compc.xml file.

So, any suggestions? Thanks.

Great plugin, I've used it a lot.

One problem with the recent FD release. I'm getting this error when trying to compile SWC:



Why is it doing this, both tools use the same compiler ?

Could it be that you are trying to compile an as3 Preloader project ? As far as I know the swc plugin expect you to use a regular as3 project, the as3 preloader project template won't work.

It is a regular as3 project and it was compiling I guess until I added the reference to EXIT_FRAME.

Thanks for your help.

Great plugin. I've been using FlashDevelop for some time now and I really like the option to create SWC code libraries. Still, I was missing some features in the plugin so I made a few changes that might be useful for others too.
1. Added an option to exclude all hidden classes/files when compiling
2. Added all global class paths to the <source-path>
3. .lxml files are not automatically created for every project opened. Only when saving "SWC Library Options"

If this is interesting to anyone - just let me know, and maybe we can add it to the official plugin.

I just ran into this on Windows 7 64-bit, FD 3.3.2 RTM.

1) My JAVA_HOME environment variable is C:\Program Files\Java\jdk1.6.0_23, and my PATH has %JAVA_HOME%\bin. Note the JDK is 64-bit.

I have the 32-bit JRE installed, so I add an environment variable for it -- JRE_32 with value C:\Program Files (x86)\Java\jre6\bin -- and add a %JRE_32% entry to my PATH, and reboot.

2) An error popup tells me I don't have MSVCR71.dll. Following this reference, I copy the file into C:\Windows\System32, and reboot.

3) I'm using the default flex SDK (4.1.0.16076). I need to make the following change in C:\Program Files (x86)\FlashDevelop\Tools\flexsdk\bin\jvm.config:

Note the forward slashes: using backslashes (i.e., pasting from Windows Explorer "copy address") yields Error: could not find a JVM.

Finally, ExportSWC works like I'm used to on XP!

Hi,

Is there an update for the ExportSWC plugin that can support multiple instances of FD?
Right now I'm getting an error each time I open a new instance of FD (first instance - no error):

The process cannot access the file 'C:\Users\xxxxx\AppData\Local\FlashDevelop\Plugins\ExportSWC.dll' because it is being used by another process.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite)
at PluginCore.Helpers.FileHelper.EnsureUpdatedFile(String file)

Thanks

This is appearing because in source code working directory for compc.exe and asdoc.exe set as project directory.
That is not necessary (I've checked out).
Warappa, please set working directory as process location. (SWCBuilder.cs#RunCompc(), SWCBuilder.cs#IncludeAsDoc())
Thanks.

Hello! I've got an error, trying to set up ExportSWC. I just installed it from the sourceforge page a moment ago, and I'm using FlashDevelop 3.3.2

I've got a project that builds in Flex Builder 3; I imported it into FD, installed the ExportSWC plugin, and ran it. After figuring out the first momentary bug of telling FD where the proper version of Flex is (for this project), the error I have coming back is:

"nothing was specified to be included in the library"

I looked in the flex.compc.xml file and indeed there is nothing specified in the <source-path /> property. (I'm guessing that this is why it's failing.) Does anyone have any idea why the config file specifies nothing to be included?

[EDIT: Never mind... Ugh! I recall now that when importing from a Flex Builder project, FlashDevelop doesn't seem to add src/ to the classpaths... ]