Quantcast Developing for BFA with standalone libraries - WoWInterface
Thread Tools Display Modes
07-22-18, 11:04 AM   #1
yess
A Deviate Faerie Dragon
AddOn Author - Click to view addons
Join Date: May 2008
Posts: 16
Developing for BFA with standalone libraries

Since BFA/8.0.1 I get a missing file error for all libraries of my own addons because the .toc has the list of libs for the release version where the files will be included.

Has anyone found an elegant solution for this problem?

#@[email protected]
libs\LibStub\LibStub.lua
libs\CallbackHandler-1.0\CallbackHandler-1.0.xml
libs\AceAddon-3.0\AceAddon-3.0.xml
...
#@[email protected]

Edit: Hmm, an inverted tag would be nice, where the lines are commented out but will not be in the release version.

Last edited by yess : 07-22-18 at 11:07 AM.
  Reply With Quote
07-24-18, 02:48 AM   #2
yess
A Deviate Faerie Dragon
AddOn Author - Click to view addons
Join Date: May 2008
Posts: 16
I found a solution that works well for me.

I moved the list of files to be included to an xml file and in that one I can use the non-debug tags:
Code:
<Ui xmlns="http://www.blizzard.com/wow/ui/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.blizzard.com/wow/ui/
..\FrameXML\UI.xsd">
  <[email protected]@
  <Script file="LibStub\LibStub.lua" />
  <Include file="CallbackHandler-1.0\CallbackHandler-1.0.xml" />
  <Include file="AceAddon-3.0\AceAddon-3.0.xml" />
  ...
  @[email protected]>
</Ui>
That way I do not get the annoying errors during development and in the released version they are included as the packer changes the tags so that the lines are not commented out.
  Reply With Quote

WoWInterface » Developer Discussions » General Authoring Discussion » Developing for BFA with standalone libraries

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

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