QtCreator: Configure default build types - qt-creator

(Disclaimer: I'm not sure if SO is the right place to ask this. If not I'd appreciate pointing me to a better place.)
Whenever I open a new cmake project in QtCreator (basically all newer versions, let's say 4.3+) my default kit is select with the following build types:
Default
Debug
Release
Release with Debug Information
Minimum Size Release
All these options are enabled by default and I have to manually disable them (I only want Debug and Release most of the time).
Is there a way to configure this?
(I've looked through the kit configuration pages and tried to consult google/qtcreator help topics.)

Related

Firefox configuration via CLI

During system setup and later for automatic testing (whether specific configuration settings are still effective) I am interested in configuring Firefox via CLI. I have seen one or the other command line tool but they would always cover only one aspect of Firefox and are usually bound to a specific version.
To be more clear about this, let me list some of the use cases for the CLI:
create/remove profiles
install/update/remove plugins
list installed plugins incl version
list configuration settings, get/set values (also for plugins)
clear cache/cookies/...
manage truststore
manage bookmarks
Is there no command line interface officially supported?
Firefox command line interface is indeed officially supported, but at this moment in time is under documented. While it's possible to find some outdated documentation, the in-tree documentation is only a stub.
Since you mentioned automated testing, you might also consider the approach currently being used by Mozilla to run tests on Firefox:
Generate a profile to be used for testing.
Tweak the preferences in the profile (e.g. using user.js).
Start Firefox using the generated profile (either using -p or --profile).
Execute your tests (with Geckodriver?).

XCode 9.4.1 breakpoint doesn't hit when release build scheme

I'm using XCode 9.4.1.
I need to hide print log when release mode, so I add #if-#endif conditions and want to check if these working correctly.
So I change my build scheme to release but breakpoint not wroking.
I found some answers on StackOverflow, and try any method that I can, but That's not working either.
Is there something else that I can try more?
Go to your build Setting set optimization level none for release.
Set Build Active Arch to Yes for release.
Set Debug information format to DWARF for release

FLORA2 v1.2 with Eclipse vizualizer plugin

Just start to play with http://flora.sf.net reasoning system.
Trying to configure
Window/Preferences/Flora-2 Preferences/Reasoner
pointing to installed D:\FLORA or D:\FLORA\flora2
have message box
Did you install Flora-2 with cygwin?
Eclipse was updated, and plugin was installed from http://flora.sourceforge.net/visualizer
and error
FLORA-2 Visualizer did not find a configured version of FLORA-2 at a default location.
Please specify the location of a configured FLORA-2 system using the following menu:
Window -> Preferences -> Flora Reasoner
PS: In real I don't need full plugin, it can be just set of flora scripts,
which can generate debugging information in visualizable form:
.dot files for GraphViz is the best variant, or some set of .svg.
PSS: maybe InterProlog Studio will be good IDE solution with some tunings.

IDEA 13 community can't debug Haxe

I use the IDEA13 community to work with the Haxe openFL. I had installed the Haxe plugin. I create a haxe project. I can run it with any target, such as Flash,HTML5, mac and so on. But I can't debug it with any target platform. To my surprise, I even not see the red point after I click the IDEA side which would appear a red point when I do the same in a java project.
Then I tried to use debug icon button to debug it. But nothing show me after the compile complete.
Can anybody know whether the IDEA13 support to debug Haxe project? if can, how can I set?
I need help.
I wish everyone goes well.
Unfortunately the community plugin does not provide debugging for all the targets.
Currently only flash and an experimental cpp debugger(tivo fork) are the only implementations provided.
For html5 the plugin requires work to integrate with idea's javascript debugger. You can however use the Haxe generated source maps for break points on Haxe source code within the chrome developer tools.
There is activity for this plugin on github so it may just be a matter of time.

Build failed... No build tools defined. AVR studio 4.19

When I tried to debug a small piece of code using AVR studio 4 I got this error:
Build failed... No build tools defined.
Could someone give me some advices?
In AVRStudio 4.19, Atmel made some serious changes from previous versions. Specially while using the toolchains. After you install WinAVR (the latest version, 2010...), open a new project in Avrstudio and from now on, everytime you make a new project you have to do this steps:
Go to "Project" tab
Go to "Configurations Options"
Then all the way down to "Custom Options".
Once you there, you'll see a checkbox called "Use AVR ToolChain", UNCHECK that option.(For some reason AVRStudio 4.19 does not link automatically the toolchain from WINAVR, so you have to do it manually).
After this, it enables the two options below.
For avr-gcc, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\bin\avr-gcc.exe
For make, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\utils\bin\make.exe
This directions depends on where did you installed WINAVR. I remember that the default location is "C:\" but when I installed WINAVR, I changed it to "ProgramFiles"
Click "OK".
After doing this steps, you should be able to compile and run your code.
Cheers, and hope it helped!
PD: I had that same problem, months ago. Check out, www.avrfreaks.net, very good webpage for newbies and pros at programming AVRs.
You need to install WinAVR or Atmel's "AVR Toolchain." If you already have one of these and still get this message, you may need to tweak the System Variables.
Connect the programmer first and then run avr studio.
I have that error when I try to open a project made in another version of AVR Studio (or upgraded to another version by someone else).

Resources