Hi all,
I have a project that has about 10+k files that are generated by doxygen from source code. However, I do NOT want Flare to try to process them and then repeatedly tell me that these files are NOT valid XHTML files. I know they're not but once generated in my help system, they display perfectly fine. But, Flare adds over 10 minutes to my build because it tries to convert each and every one of these files and tells me each and every file is not valid XHTML.
Is there a way to mark an entire directory in my content directories so that Flare will just pass them through and not try to do anything with these files? 99% of my log is the same message that the doxygen-generated files are not valid XHTML.
Thank you in advance.
Is there a way to ignore files during a build?
Re: Is there a way to ignore files during a build?
sanjsrik, WAY back when (not trying to show my age here 
) the help authoring community referred to this as "baggage files". I think the RoboHelp product supports this. I know nothing about doxygen, but it does not appear there is a way to include files in your Flare project and also have those same files appear in the output where Flare has "completely ignored" them. Question is why is there a need to include the 10K+ files in the project folder to begin with? Why not just take the doxygen output and move it directly to the folder you want, without any Flare intervention at all? I guess what I'm not understanding but nevertheless curious about is if you don't want Flare to have to process them, why include them in the project?
) the help authoring community referred to this as "baggage files". I think the RoboHelp product supports this. I know nothing about doxygen, but it does not appear there is a way to include files in your Flare project and also have those same files appear in the output where Flare has "completely ignored" them. Question is why is there a need to include the 10K+ files in the project folder to begin with? Why not just take the doxygen output and move it directly to the folder you want, without any Flare intervention at all? I guess what I'm not understanding but nevertheless curious about is if you don't want Flare to have to process them, why include them in the project?Re: Is there a way to ignore files during a build?
I'm including them in my Flare project Contents folder because they are part of a build process generated in the Unix environment that runs a Make file to product both C++ and Java doxygen files. The Jenkins job that kicks off the build syncs my Flare project through the git repository where the doxygen files are stored in the Contents directory. The files are also linked from the TOC to the classes.htm files to the C++ and Java doxygen files, respectively, that then shows them as part of my final build. If I don't include them in the Flare project, Flare will see these as broken links or unreferenced links in my Flare project and ignore the link from the TOC to the classes.htm files in the C++ and Java doxygen output.
I remember the concept of baggage files (used to use RoboHelp when it was still owned by Bluesky, how I miss the massive kadov tag fiasco). I was just hoping that there was an ignore command or something that I could accomplish through conditions that would allow the directories to be ignored and just passed through.
I find it interesting that Frame to Flare integration has the ability to do this from Frame to Flare but not natively in Flare to output.
Thanks for the answer. Guess I'll have to figure something out. This is more of an annoyance than something that is stopping me from creating output.
I remember the concept of baggage files (used to use RoboHelp when it was still owned by Bluesky, how I miss the massive kadov tag fiasco). I was just hoping that there was an ignore command or something that I could accomplish through conditions that would allow the directories to be ignored and just passed through.
I find it interesting that Frame to Flare integration has the ability to do this from Frame to Flare but not natively in Flare to output.
Thanks for the answer. Guess I'll have to figure something out. This is more of an annoyance than something that is stopping me from creating output.