I've built the Docset for my code, and I'm trying to get Xcode to compile the Docset when I perform a build. However, Xcode doesn't see the docset once it builds (The DocSet is visible in the directory).
Here's my process:
1) Generate the doxygen output
doxygen doxygen.config
2) go into the html directory and generate the docset
make
[...]
14: MyCodeIOSDecoder_8h.html
15: MyCodeIOSHighLevel_8h.html
Loading symbols from [...]/source/html/org.doxygen.Project.docset/Contents/Resources/Tokens.xml
* 93 tokens processed ( 0.0 sec)
Linking up related token references
Sorting tokens
3) installing doc set
make install
[...]
cp -R org.doxygen.Project.docset ~/Library/Developer/Shared/Documentation/DocSets
4) no docset in xcode 4, maybe old doxygen version Doxygen version 1.7.4-20110629
double check where the docset should appear in Xcode 4
Am I missing something?
Let's assume Doxygen output folder is ~/Documents/myDocSet.
Inside, there's the folder html.
Make sure the doxyfile includes
GENERATE_DOCSET = YES
Open the terminal
cd ~/Documents/myDocSet/html
make install
Launch the Applescript loadDocSet.scpt
tell application "Xcode"
load documentation set with path
"~/Library/Developer/Shared/Documentation/DocSets/myDocSet.docset"
end tell
Related
I want to use Bullseye Code Coverage for Qt. But, I can not set the environment.(Qt creator)
I found below links and follow https://www.bullseye.com/help/tool-qtCreator.html
Bullseye Code Coverage for Qt
step1. I added below at main.pro
QMAKE_CC = "\"C:/Program Files (x86)/BullseyeCoverage/bin/gcc\""
QMAKE_CXX = "\"C:/Program Files (x86)/BullseyeCoverage/bin/g++\""
QMAKE_LINK = $$QMAKE_CXX
QMAKE_LINK_C = $$QMAKE_CC
step2. I checked the Makefile.Debug.
MAKEFILE = Makefile.Debug
####### Compiler, tools and options
CC = "C:/Program Files (x86)/BullseyeCoverage/bin/gcc"
CXX = "C:/Program Files (x86)/BullseyeCoverage/bin/g++"
But step3, How can "Enable coverage build" ??
Can anyone easily explain the next steps?
For anyone having the same issue, the "Coverage Build" is a Bullseye option, accessible from its Tools menu (i thought it was some QtCreator's option).
Once you have done steps 1. and 2. in the OP question:
go to Bullseye and activate the Coverage Build (if you don't activate it, a normal build will be made)
Compile
A test.cov file should appear in the Qt project's build directory
Create a COVFILE environment variable whose value is the full path to the test.cov file
Restart QtCreator and rebuild
One thing that helped troubleshooting was looking at the "Compile Output" in QtCreator. If COVFILE is correctly set, its value will be shown. If it isn't, the coverage statistics will be most likely empty.
I want to use FTP in my current project, but since Qt5 ftp isn't available (only as add-on).
I downloaded the sources from here: https://github.com/qt/qtftp
In Qt's forum, I found a instruction how to use it:
Open Console in the qtftp-folder
Generate the headers: cd qtftp, <QTDIR>/bin/syncqt.pl -version 5.2.0
Run qmake
Run make (mingw32-make)
Run make install (mingw32-make install)
Add QT += ftp in my .pro-file
Run qmake on my project
compile my project.
(https://forum.qt.io/topic/23904/qtftp-and-qthttp-compatibility-add-ons-for-qhttp-and-qftp-classes-in-qt-5)
So, I wanted to try these steps, but it fails on the first step, because the syncqt.pl cant be found, but I looked in the Qt-directory, and the file is there.
Anybody has an idea, how to fix/solve this? I am using Qt5.9.1
If you have downloaded the portable version of strawberry-perl like me, just extract .zip somewhere on your disk. After that, open the portableshell.bat (it should open a command prompt window)
After that, you can type in the code of step 2, and don't forget to add the -version argument.
Then you can continue with step 3, and everything should work without any problems.
I have installed elm-format package (using amp install elm-format) and I want to run it from the command line , example elm-format mypage.elm
In order to run it from the command line it should be available in one of the environment path let's say usr/local/bin while the elm-format directory is installed in the following path Users/myuser/.atom/packages and none is available in env path
what should I move to the PATH (usr/local/bin) , is the whole folder or an executable file
note : when i run ls Users/myuser/.atom/packages/elm-format i get the followings :
CHANGELOG.md README.md keymaps menus src
LICENSE.md example lib package.json
I will answer my question since I have solved it.
first you have to install the elm-format binary file using your browser form the following URL
after installing the binary file extract it add the path to the environment path
for windows user add elm-format.exe or mac user add elm-format
since I am a mac user I used the below command to add it :
mv ~/Download/elm-format /usr/local/bin/elm-format
after installing the binary now we need to install elm-format extention for the appropriate editor
since I am using atom editor I have used the following command apm install elm -format
now we can used elm-format command line to format the elm page
command line : elm-format pagename.elm
According to npm website You could install elm-format by npm install -g elm-format.
For anyone using VS Code (on a Mac / Linux system):
1) Choose Download ZIP in the 'Clone or Download' dropdown on the elm-format Github repo.
2) To move the elm-format executable to your 'PATH', open the Terminal application and enter the following command:
mv ~/Downloads/elm-format /usr/local/bin/elm-format
3) Open VS Code and install the extension elm-format.
4) Still in VS Code, open User Settings. (Do this by pressing CMD + SHIFT + P to open the available commands search bar and type User Settings -- press enter. Alternatively, you can use the shortcut CMD + , to open the User Settings.)
5) In the file that shows up on the right side of the editor (your personal settings overrides), add the following line:
"elm-format.formatOnSave": true
Save.
Cheers!
For Atom configures: https://atom.io/packages/language-elm for Syntax highlighting and autocompletion, for auto format on saving https://atom.io/packages/elm-format
For the others IDE https://guide.elm-lang.org/install.html (VScode, Atom, Sublime, Vim,...)
All,
I am (trying to) using Netbeans to build a simple Qt app (from a tutorial) and I cannot build it because I get this error:
/C/Qt/2010.02.1/qt/qmake/qmake.exe VPATH=. -spec win32-g++ -o qttmp-Debug.mk nbproject/qt-Debug.pro
make[1]:/C/Qt/2010.02.1/qt/qmake/qmake.exe: Command not found
when the file is exactly there, and I can open a terminal and execute it.
Note in the error message: "/C/Qt..." The actual path is C:/Qt...
I have used the tools/options/c++ dialog to browse to the file and select it, and it is specified as C:\Qt... just like all the other tools. What is corrupting the C: and making it /C/ ?
Now, if I remove the path to qmake, and have it use the PATH environment variable, it finds it, but then it fails due to 'multiple targets'...
Obviously, pilot error, but where? I have seen several posts on this, and they all say to make sure it is in the path, and it is, so now what? (I can open a terminal and type 'qmake' and I get the 'Usage: qmake..." so I know it is visible.
Windows 7, Netbeans 7.0, MinGW (I also have cygwin installed...).
Any and all help greatly appreciated.
:bp:
Addenda: I changed the path to my 'make' to use the MinGW one rather than the cygqin one, and now it can find qmake, but I get other errors: 'Could not find mkspecs for your QMAKESPEC(win32-g++) after trying:...
Any additional thoughts?
QMake requires more than just a path to work correctly. On my Windows box, there is a menu option for 'Qt Command Prompt' under the 'Qt SDK 2010.05' group in the Start Menu. Running it produces the following:
Setting up a MinGW/Qt only environment...
-- QTDIR set to C:\Qt\2010.05\qt
-- PATH set to C:\Qt\2010.05\qt\bin
-- Adding C:\Qt\2010.05\bin to PATH
-- Adding C:\WINDOWS\System32 to PATH
-- QMAKESPEC set to win32-g++
You will want to make sure the environment you launch qmake in has all of those set.
The most probable reason you are see '/C/...' is because you are causing a mingw shell to run when you execute your build.
HOw do I build docsets in Xcode 4 with Doxygen?
Apple's documentation refers to Xcode 3 and doesn't seem to apply to Xcode 4.
I think it might have to use a schemas (schemata?) rather than targets, but I'm not 100% certain.
Thanks in advance...
You can build documentation as part of a dedicated target:
In the project navigator, click on the project.
In the right pane, add a new aggregate target (in MacOSX/Other) and name it Documentation
In this target, add a new Run Script build phase
In this build phase, invoke the Doxygen command line:
/Applications/Doxygen.app/Contents/Resources/doxygen
Once the DocSet is built, copy it into /Users/<YourName>/Library/Developer/Shared/Documentation/DocSets folder.
The new docset should appear into the help browser.
It seems documentation for Xcode 3 works fine with Xcode 4.
I followed instructions (see Using Doxygen to Create Xcode Documentation Sets on Documentation) and everything is fine excerpt Xcode does not load the brand new docset.
I then examined the AppleScript command on the given run script and tested it on AppleScript editor : execution result was false. Error was the name of the docset file was missing.
By adding the docset filename the AppleScript script run successfully and the docset is well inserted to documentation :
Before :
echo "load documentation set with path \"/Users/$USER/Library/Developer/Shared/Documentation/DocSets/\""
After :
echo "load documentation set with path \"/Users/$USER/Library/Developer/Shared/Documentation/DocSets/com.mycompany.DoxygenExample.docset\""