Fantastic. The issue tracking that one is
https://bugs.launchpad.net/mudlet/+bug/1371444. I haven't tracked down
what is making the backgrounds go black once the mapper is opened
though.
** Changed in: mudlet
Status: New = Invalid
--
You received this bug notification because you are a
Well, this was definitely an environment issue, but the cause of which
we will never know. I figure if I'm having so much trouble with a simple
build, it's probably going to affect me in my professional development
sooner or later and started with a totally fresh OSX.
Compile worked great this
I gave a go at replicating it on 10.10 however Qt was stuffing up and it
all died when I rebooted.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1413037
Title:
Mudlet 3.0.1 Build error on OS X
Yeah, that sounds consistent with my experience.
If you install qt the homebrew you need to reference qmake via full
path. Something like /usr/local/Cellar/qt5/bin/qmake.
Not that you didn't already know that, but it was a gotcha for me coming
from Linux.
--
You received this bug notification
Try Qt 5.4.0 perhaps?
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1413037
Title:
Mudlet 3.0.1 Build error on OS X 10.10.2
Status in Mudlet the MUD client:
New
Bug description:
I'm not
nate at macbook-air in ~/s/c/m/src (development)
↪
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
-v
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin14.1.0
Thread model: posix
I've been experimenting a bit with this. Here's my output when I try to
use -spec macx-g++ (which is default): http://pastebin.com/GQnhZwKj
Here's my output when I use -spec macx-xcode and then use xcodebuild
instead. Same errors, this time it's just running 'moc' against them
first as far as I
Maybe you need to change the dialect as described here:
https://stackoverflow.com/questions/16999749/expected-at-the-end-of-declaration-list
? We're using C++11.
On Fri, Jan 23, 2015 at 9:05 AM, Nate Cox 1413...@bugs.launchpad.net
wrote:
I've been experimenting a bit with this. Here's my output
Bah.
So, I removed both xcode and xcode-beta from my system, reinstalled
xcode, crushed my mudlet install and cloned down again.
qmake now gives me the proper location of clang and clang++, as below
--
nate at macbook-air in ~/s/c/m/src (development)
Hmm. We'll get there, don't give up - it's possible. Could you paste the
latest build log using that setup - it'll help in showing to others.
On Fri, Jan 23, 2015 at 8:25 AM, Nate Cox 1413...@bugs.launchpad.net
wrote:
Bah.
So, I removed both xcode and xcode-beta from my system, reinstalled
I installed both via Qt's online installer and Homebrew, neither of them
setup a link for some reason. Qt's one was plain broken though:
http://pastebin.com/gnakm477. Homebrews worked fine, I forgot to try
that, here is the log: http://pastebin.com/aegHbMBp
So 10.10 compiplation is possible.
Welp, that's not it then. Hit some Apple forums up or try asking on
stackoverflow.com, it definitely just seems to be an issue with your
environment since mine was able to work. on 10.10.
Have you run the two scripts in CI/ folder, pre install and install for
OSX?
On Fri, Jan 23, 2015 at 6:12
Here's the -v for both of the clangs referenced in the Makefile:
nate at macbook-air in ~/s/c/m/src (development)
↪
/Applications/Xcode-Beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++
-v
Apple LLVM version 6.0 (clang-600.0.54)
I did run both of those scripts, it seems like they just set up the
homebrew requirements which I already had.
I'm curious to know what it is that I changed which is giving me so many
problems.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed
On a fresh install of 10.10, this is what I did - install Qt 5.4 from the
online installer, Install XCode 6.1 and the command-line tools for it, then
run those scripts (which installed qt5 again) and used the Cellar qmake in
the end.
By the way the clang used to build was
I think this may have to do with the version of clang, but I don't
really have enough knowledge on the subject to find a real solution.
Guess I'm giving up on this for now; haven't made any headway.
--
You received this bug notification because you are a member of Mudlet
Makers, which is
The output seems to be corrupted with ANSI colouring thrown in.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1413037
Title:
Mudlet 3.0.1 Build error on OS X 10.10.2
Status in Mudlet the MUD
That's output from the `screen` command; if you `cat` the output in a
terminal you'll see the exact representation including syntax
highlighting.
I'll add a plain text version as well.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to
Someone else having an issue here, but the issue resolution is unclear:
https://github.com/biometrics/openbr/issues/198
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1413037
Title:
Mudlet 3.0.1
** Attachment added: plain text build errors
https://bugs.launchpad.net/mudlet/+bug/1413037/+attachment/4302735/+files/build_errors_plain_text
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
I saw that one; it's actually a duplicate of another issue on that repo,
which is also dead with no answer. I asked for an update, hopefully
somebody knows the solution offhand.
--
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
21 matches
Mail list logo
