I was trying to build QtD using the instructions here:
http://www.dsource.org/projects/qtd/wiki/BuildWindows
I downloaded the repo.
Went inside the repo (it was called repo and not qtd as the instructions said).
I created the build_dir dir and went inside there.
I used the:
cmake -G"MinGW Makefiles" ../
Command and then I got the following error:
Error: CMake: Could not create named generator MinGW Makefiles
Taking advice from a friend I went inside the d2 directory and went inside the qtd dir there, and repeated the steps above.
Same error.
I have the components the instructions listed, and with what I believe is needed on my PATH
What am I doing wrong? Are there any other instructions I'm missing?
I'd heard that QtD was no longer maintained. Certainly, the last commit on dsource was 3 years ago: http://www.dsource.org/projects/qtd/browser
However, the d wiki has a link to bitbucket where someone has a version of it which had a commit as recently as December. So, I guess that someone revived it and put it up on bitbucket.
However, regardless of whether the bitbucket repo is now indeed the "official" QtD repo, given that the last commit to the dsource repo was 3 years ago, the odds are very high that it no longer compiles, even if you use the correct build commands. So, I'd advise checking out the bitbucket repo and seeing if you can get that to work rather than trying to get the version on dsource to work. And even if you could get the dsource version to work, it's clearly unmaintained, so you're not going to want to use it long term, whereas the bitbucket version does appear to have had work done on it relatively recently.
Related
I'm trying to compile the examples under cpp starting with minimal_build. I don't have much cmake experience. Must this be run under docker, or can it just be compiled in a Linux shell? I'm running Centos7 on a AWS EC2 instance, and I've installed cmake 3.20.2. Executing sudo ./run.sh, errors immediately with "cd: /io: No such file or directory". When I try and make what I think are the necessary changes to the scripts, I keep hitting errors. So I just want to see is this is even possible before proceeding further.
Thanks.
Yes, it is possible. I recently built Arrow on CentOS 7. With any C++ project there are going to be challenges switching amongst Linux distributions. The docker image is a way to provide a single example that the Arrow project can verify. You will need to adapt your Linux environment based on the issues you encounter. #Tsyvarev is also correct, you will want to use run_static.sh instead of run.sh. In order to do this you will need to dive a bit further into the details.
The build script has two steps. First, it will build the Arrow project itself. This is probably going to be the more challenging step. This guide is helpful for this step and provides a lot more detail into how Arrow builds and what options there are. The second step will be to compile and build the example.
Specifically for CentOS 7 one of the challenges you will face is that you will need a newer version of CMake. I ended up building CMake from source. If you go this route you also need to make sure that CMake is built with curl/https support. I used the --system-curl option for this.
That is all I remember having to do special for CentOS 7 at the moment. As you go about this task if you run into further, more specific, issues, feel free to ask them here or on the Arrow dev/user mailing list.
I have the latest version of Swiftlint (via brew). When I check github, I see that they have added a bunch of rules since the release, even a few a couple of days ago. How do I get those rules onto my mac? Do I have to uninstall the version I have and reinstall the same version? (will that even get the new rules?) Do I have to download the zip from github?
Use brew update. But some of the new code is not yet in the release branch. For the dev-branch you would need to pull the newest version manually. It is a shame that the new documentation on rules is so poor, because i ran into the exact same problem.
I would suggest waiting until the rules are in release branch and are deployed by brew. Sometimes those rules can be buggy and are not reliable.
An alternative to brew update is to integrate SwiftLint using CocoaPods, and in that case you would update it with pod update.
I recommend the CocoaPods approach as it garanties that all co-developers get the same errors (and warnings), and avoids situations were one developer doesn't get any error, pushes code and confronts another developer to build errors.
I have a strange issue on my Xcode 6. Today I worked at home and when finished a part of C++ code, I committed it on my personal git remote server.
Okay then I came to work, successfully checked it out and then built it. The first build was as usual, it took a few minutes to compile, but other one I made after correcting a code, simply have been done in a few milliseconds, like Xcode took a previously built version and use it this time.
And that was it! I notice I've got the previous functionality, like I use the first version of code, which I checked out after start my work computer.
So the question is - how to force Xcode 6 automatically clean the previous builds before compiling?
P.S. I also noticed that breakpoints changed their color from blue to gray. What have I done wrong here?
Resolved.
Looks like the matter in file's owner permissions. Trying to do sudo chown -R boss:staff /Users/boss/Codes/ made the issue gone.
I am trying to install LibQxT to use it with Qt5, so I downloaded the sources and as soon as I run the configure.bat there is an error:
LibQxt requires 4.3 or newer but Qt 5.2.1 was detected.
Searching on the web Ive found out that apparently it doesnt know the correct path to the qconfig.pri (as seen here (last post)) so it doesnt really detect the version.
I have tried adding the path to the variable QTDIR in the ways described in the post (I tried to do it in the qmake cache located in the Libqxt folder and tried to define it as a environment variable). I havent found any clear solution to this problem, so I hope someone knows by now how to solve this issue.
Thankyou.
EDIT
What #vahancho said its true, if its not detecting the version, why does it name it? Perhaps its not detecting it properly.
But if it is, why cant it see that my version is higher than the requested one?
I have located the error and it fails at some point betweeen the echos and the if:
echo Configuration successful.
echo Generating makefiles...
cd %QXT_BUILD_TREE%
%QMAKE_BIN% %MSVCMODE% -recursive %QXT_SOURCE_TREE%\libqxt.pro
if errorlevel 1 goto mainqmakeERR
You can try to use the latest development branch of libqxt which could be found here. It will be compiled with Qt 5. You can just clone one copy of the source code by:
git clone https://bitbucket.org/libqxt/libqxt.git
http://code.google.com/r/hectorchu-go-windows/source/list
If you could compile it successfully, I like to know the procedures of how to.
Assuming you are using Hector's source tree:
Install MinGW and MSYS, along with MSYS Bison and any other tools you think you'll find useful (vim, etc).
Install ed from the GNUWin32 project.
Install Python and Mercurial.
Clone the [hectorchu-go-windows mercurial repository](https://hectorchu-go-windows.googlecode.com/hg/ hectorchu-go-windows) to C:\Go.
Run an MSYS shell (or rxvt). The rest of these are bash commands...
mkdir $HOME/bin
export PATH=$HOME/bin:$PATH
export GOROOT=C:\\Go
export GOARCH=386
export GOOS=mingw
cd /c/Go/src
./all.bash
Correct errors as it spits them out at you, repeat step 10 until it starts building.
It's the same idea as on Linux or MacOS, basically.
However, I still stand by what I said in my comment above: this isn't necessarily going to generate anything that actually works yet. You'd be better served by waiting until this effort has merged into the main Go tree before tackling it, unless your interest is in assisting with the porting effort.
Update: there is now a mostly-functional pre-built windows port available, for those not interested in building the compiler themselves. However, given the rate of change of the project, the lack of formal releases (other than the hg "release" tag), and the possibility of Hector's changes being merged into the main branch soon, keeping up with development via source builds is likely to produce better results over time.
Just FYI, there is seems official one now.
http://code.google.com/p/go-windows/
Hector said he was only able to get as far as being able to compile and run an empty main. See issue 107:
http://code.google.com/p/go/issues/detail?id=107
There is still a lot of work to do in porting that, especially since the code has lots of dependencies on ptrace and syscall, not to mention the different threading models between Linux/BSD and Windows.
Update:
There's a new thread on golang-nuts (started 26.03.2010) with a link to a recent build and some current building instructions (using MinGW+MSYS).