The swc '/Applications/Adobe Flash Builder Burrito/sdks/4.5.0/frameworks/libs/framework.swc' has style defaults and is in the library-path, which means dependencies will be linked in without the styles.

~ lupin

The swc ‘/Applications/Adobe Flash Builder Burrito/sdks/4.5.0/frameworks/libs/framework.swc’ has style defaults and is in the library-path, which means dependencies will be linked in without the styles. This can cause applications, which use the output swc, to have missing skins. The swc should be put in the external-library-path.

I don’t know the answer to this. Please add an answer in the comments.

Update
Hershel posted a solution in the comments and I’ve pasted here:

This happens when a added swc has link selection ‘merged into code’. It should be default external.

Since both the libraries have style defaults.css files, the compiler overrides the added swc’s defaults.css

Remedy : Go to build path, and select the conflicting swc, open the node, go to link type, and select edit, and then select ‘external’
save, clean build !

3 thoughts on “The swc '/Applications/Adobe Flash Builder Burrito/sdks/4.5.0/frameworks/libs/framework.swc' has style defaults and is in the library-path, which means dependencies will be linked in without the styles.”

  1. I’m getting this for airspark.swc while building a swc that does not, as far as I can tell, have any UI at all.

    Like

    Reply

  2. This happens when a added swc has link selection ‘merged into code’. It should be default external.

    Since both the libraries have style defaults.css files, the compiler overrides the added swc’s defaults.css

    Remedy : Go to build path, and select the conflicting swc, open the node, go to link type, and select edit, and then select ‘external’
    save, clean build !

    Liked by 1 person

    Reply

Leave a comment