Qt Controller Scripting select components in ComponentSelectionPage - c++

Im using a script to automate the QtFramework installation. I was used to select all components in the ComponentSelectionPage. However nowadays with Qt5.10.0 this results in over 11 GB. So i would like to pick just the components i need. According to the documentation the ComponentSelectionPage has selectComponent(id) and deselectComponent(id) methods, id beeing the name of the component. So this should be doable.
However i can't find any documentation on the names/ids of the components. I tried several things like:
widget.selectAll()
widget.deselectComponent("MSVC 2013 64-bit")
widget.deselectComponent("MSVC*")
widget.deselectComponent("*MSVC*")
But neither of those work (i tried a bunch of differnt other combinations also). So does anybody know where to find documentation about component names of the default Qt Installer? I was already poking in their git repository but could not find anything.

so i've found out how to solve this quite a while ago, if someone is still interested:
By running strings <qt-installer-executable> | grep "qt\." i was able to extract the names of the components. (Not sure if it was strings in windows, but a similar tool exists for sure).
An example output is then something like
....
qt.qt5.5121.gcc_64
qt.qt5.5121.examples.qtpurchasing
qt.qt5.5121.doc.qtscript
qt.qt5.5121.qtdatavis3d.gcc_645
qt.qt5.5121.qtscript
qt.qt5.5121.doc.qtpurchasing
qt.qt5.5121.examples.qtscript
qt.qt5.5121.qtnetworkauth.gcc_64
...
along with a lot of other stings.

Related

Rename NIC in opensuse

I'm using opensuse 13.1, and I need to rename my NIC from 'em1' to 'eth0'. While I've found several other people trying to rename NICs, I haven't found anyone who seems to be doing it in Suse 13.1. One of the frequently mentioned fixes is changing parameters in the
70-persistent-net.rules file, but mine is empty. I also haven't been able to find anything in Yast that has NIC names, but that doesn't mean it isn't there.
If it helps, here's an example of someone doing in Red Hat what I'm trying to do:
http://www.sysarchitects.com/em1_to_eth0.
The problem here is that the pathways he references don't always match up with mine (for example, I don't have /etc/grub.conf, nor do I know if I have an equivalent and if I do where to find it), so I haven't been able to use this example to get mine working.
Thanks for the assistance!
openSuSE 13.1 uses grub2. You will not have an /etc/grub.conf. The change in network interface names is a result of running systemd/udev >= 197. You are in luck, you can change the device name. Look at the freedesktop.org page list below (the folks that brought you systemd/udev)
You basically have four options. The four options are detailed here Predictable Network Interface Names (I don't like this, how do I disable this?) It is toward the bottom of the page.

How to write to, edit, and retrieve specific cells from an Excel doc with C++?

Basically, I want to be to be able to pass data between Excel cells and
my C++ program. I don't have any experience in Excel/C++ interactions and I haven't been able to find a coherent explanation or documentation on any websites. If someone could link me some references or provide one themselves it would be much appreciated. Thanks.
If this is for a Windows system, you could always use one of the available managed Excel libraries, such as OfficeWriter or Aspose.
There also might be similar libraries specifically for c++, I know we (OfficeWriter) used to make one.
Edit: Looks like there are a few out there, like LibXL and BasicExcel.
If the application will run on an end user machine with Excel installed, you can easily use the Excel interop and keep Excel hidden.
In addition to LibXL and BasicExcel mentioned by smoore, there is:
ExcelFormat Library is an improved version of the BasicExcel library and will allow you to read and write simple values. It is free.
xlslib will also read and write simple values, I have not tried it tho. It is also free.
Number Duck, is a commercial library that I have written, It supports reading and writing values, formulas and pictures. The website has examples of how to use the features.

Netbeans - copy highlighted regex search results

I made a simple regex search in Netbeans 7.3 on Windows (using Ctrl+F):
\{\{.*?\}\}
The results get highlighted correctly and the question is - how to extract highlighted text search results? Let it be copying to clipboard, saving as file or whatever else.
Is there any method doing this?
Maybe someone has any suggestion of alternative quick approach to such task in Netbeans? (or other editor)
What OS are you running? If OS X or Linux, read on!
I'm not sure about automatically copying the highlighted results to the clipboard, but I do workaround this quite a bit as well.
The easiest way to accomplish this for me without leaving NetBeans is to simply open a built in terminal window through Window>Output>Terminal (in 7.2.1) - I then navigate to my project, and run the RegEx that I built in the Find feature with my tool of choice. In fact, I use the built in terminal for this type of quick stuff in NetBeans quite a bit. If running Linux, using clipboard tools like xsel (http://linux.die.net/man/1/xsel) in combination with a built in terminal emulator can allow for devising some nice workflow shortcuts within IDEs if you are more comfortable working/coding at a terminal. Note that built in terminal emulators like the one in NetBeans is likely not going to play nicely with cut/copy/paste using the mouse, for various reasons that I won't get in to here.
As far as a built in/extension based solution for something like this, it would be helpful! I am not aware of one.
Hope this workaround helps in the meantime.

Building Boost on OpenVMs

I’m hoping to port an application to open vms using HP C++7.3, but at the minute just trying out a few examples to establish if it's a potential way forward but a bit stuck. Being completely new to open vms it's being a lot of fun so far.
For starters I've not got very far building boost as a whole, after some googling I found a few mentions of people having dcl scripts to build boost but no actual scripts. I don’t suppose anyone has any or can pint me to some. I ‘only’ need asio and threading.
Currently I’m just trying to compile the asio chat examples. And as I said I’m completely new to VMS and the compiler, I managed to get a few things to compile but now get a “could not open source file "sys/select.h"’, a bit of googling suggests I may need to have an HP porting library installed or maybe I’m just missing an prepocessor directive to include the correct code, can’t see anything obvious in socket_types.hpp to set?
Any pointers in the right general direction would be gratefully appreciated.
No answers since the questio is too open ended and in a realm I know little about.
Just some thoughts.
Select can be provided by the OpenVMS TCPIP services (aka UCX), or other TCP stack.
At the dcl prompt try: $ HELP TCPIP_Services Programming_Interfaces Socket_API
Async programming on OpenVMS is typically 'event driven'.
Google for SYS$QIO and AST
There is a public access OpenVMS system which holds 'NOTES FILES' (pre-cursor to web-forums)
Try TELNET to EISNER.DECUS.ORG and you'll get sign up instructions.
Once you are in find your way to the PORTING_TO_VMS conference
Once in the NOTES conference you can issue the command DIRECTORY or DIR/TIT=xxx
Unfortunately there is not topic for select, but you can find some interesting
reading using NOTES> SEARCH "select(" followed by repeated SEARCH commands)
( $ NOTES ... OPEN PORT ... SEARCH "select(" ... SEARCH [] ... SEARCH ... )
The PERL folks did an admirable job getting open stuff to work on OpenVMS.
Good luck!
boost library on OpenVMS can be used directly from headers.
I remember one thing to make sure was that BOOST logical is defined concealed, so the relative-includes work.

How do you parse the XDG/gnome/kde menu/desktop item structure in c++?

I would like to parse the menu structure for Gnome Panels (the standard Gnome Desktop application launcher) and it's KDE equivalent using c/c++ function calls. That is, I'd like a list of what the base menu categories and submenu are installed in a given machine. I would like to do with using fairly simple c/c++ function calls (with NO shelling out please).
I understand that these menus are in the standard xdg format.
I understand that this menu structure is stored in xml files such as:
/home/user/.config/menus/applications.menu
I've looked here: http://www.freedesktop.org/wiki/Specifications/menu-spec?action=show&redirect=Standards%2Fmenu-spec but all they offer is the standard and some shell files to insert item entries (I don't want shell scripts, I don't want installation, I definitely don't want to create a c-library from the XDG specification. I want to find the existing menu structure). I've looked here: http://library.gnome.org/admin/system-admin-guide/stable/menustructure-13.html.en for more notes on these structures. None of this gives me a good idea of how determine the menu structures using a c/c++ program.
The actual gnome menu structures seem to be a horrifically hairy things - they don't seem to show the menu structure but to give an XML-coded description of all the changes that the menus have gone through since installation. I assume gnome panels parses these file so there's a function buried somewhere to do this but I've yet to find where that function is after scanning library.gnome.org for a couple of days. I've scanned the Nautilus source code as well but Panels seem to exist elsewhere or are burried well.
Thanks in advance
After much painful research... it seems the most stable approach is to take the gnome menu parsing code, rip it of the tar ball and use it locally.
The version I used is here:
http://download.gnome.org/sources/gnome-menus/2.28/gnome-menus-2.28.0.1.tar.gz
This code loudly proclaims that it shouldn't treated as any kind of API so one is forced to, as I said rip it of the gnome tree and keep a local copy for one's own application (gather than dynamically linking to a library).
The KDE version of the menu-parsing code seems like it could be used more transportably but actually depends heavily on KDE's virtual file system. As far as I can tell, the code gnome works stand-alone. The test-file can serve as a template for doing your own parsing.