On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers have been set to '1.1+git' on master.
Cool, I
On 03/29/2014 08:31 AM, Scott Talbert wrote:
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the
release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the
release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers have been set to '1.1+git' on master.
Cool,
On Sat, 29 Mar 2014, Scott Talbert wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the
release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers have been set to '1.1+git' on master.
Cool,
On 03/29/2014 05:18 PM, Scott Talbert wrote:
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the
release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Release is out. Windows binaries are up.
I tweaked a few things about the windows binary instructions after the
release
(I was copy-pasting this time and found a few minor bugs/typos).
Version numbers have been set to '1.1+git' on master.
Cool,
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Yes, but I thought you were trying to avoid requiring the user to have the
official software installed? If the official software is installed, there
should be a DHCP server there also. At least there is on Windows.
No, I mean I assume OSX has a
On Sat, 29 Mar 2014, Phil Dibowitz wrote:
Yes, but I thought you were trying to avoid requiring the user to have the
official software installed? If the official software is installed, there
should be a DHCP server there also. At least there is on Windows.
No, I mean I assume OSX has a
On Wed, 26 Mar 2014, Phil Dibowitz wrote:
Yes, your binaries work.
Got nsis working, but there was no libgcc_s_sjlj-1.dll or libstdc++-6.dll in
my root... the attached installer is without them. I assume they'll work given
my previous tarball didn't have them.
Uh oh. When I tested your
On 03/26/2014 06:17 AM, Scott Talbert wrote:
I didn't see anything related to the installer in this most recent patch.
Did you send an older one instead?
Whoops!
New patch attached...
The other patch is committed, with your tweak of course. This is on top of
that, and not yet committed.
--
On Wed, 26 Mar 2014, Phil Dibowitz wrote:
I didn't see anything related to the installer in this most recent patch.
Did you send an older one instead?
Whoops!
New patch attached...
The other patch is committed, with your tweak of course. This is on top of
that, and not yet committed.
On Wed, Mar 26, 2014 at 08:19:17PM -0400, Scott Talbert wrote:
On Wed, 26 Mar 2014, Scott Talbert wrote:
I didn't see anything related to the installer in this most recent
patch.
Did you send an older one instead?
Whoops!
New patch attached...
The other patch is committed,
On Tue, 25 Mar 2014, Phil Dibowitz wrote:
Did you want me to do something with the libconcord-3.dll and
concordance.exe?
Can you try them and tell me if they actually work. :)
Yeah. Technically, we need to include more than just those 2 files - we
need to include all the dependent
On Tue, 25 Mar 2014, Phil Dibowitz wrote:
Did you want me to do something with the libconcord-3.dll and
concordance.exe?
Can you try them and tell me if they actually work. :)
Yeah. Technically, we need to include more than just those 2 files - we
need to include all the dependent
Scott,
Here's what I got for a Changelog after going through the git logs... seem good?
1.1
Released:
p...@ipom.com:
- libconcord: fix firmware dump file generation so we can read files we create.
- libconcord: bindings: perl bindings work again
- libconcord: mac: revamp instructions, include
On Sun, 23 Mar 2014, Phil Dibowitz wrote:
Scott,
Here's what I got for a Changelog after going through the git logs... seem
good?
1.1
Released:
p...@ipom.com:
- libconcord: fix firmware dump file generation so we can read files we
create.
- libconcord: bindings: perl bindings work
On 03/23/2014 02:35 PM, Scott Talbert wrote:
On March 23, 2014 5:16:38 PM EDT, Phil Dibowitz p...@ipom.com wrote:
On 03/23/2014 02:07 PM, Scott Talbert wrote:
Yep, that sounds about right. I think the biggies, from a user
perspective, are, fixing the Mac/Windows builds and the Harmony
On Sun, 23 Mar 2014, Phil Dibowitz wrote:
OK, I checked in that Changelog, and the version number bump to start preping
for release.
I was looking into MinGW... and uh, I think I'm missing something.
I installed mingw32, mingw64, mingw64-tools and ... well every other mingw
package I could
On Sun, 23 Mar 2014, Scott Talbert wrote:
OK, I checked in that Changelog, and the version number bump to start preping
for release.
I was looking into MinGW... and uh, I think I'm missing something.
I installed mingw32, mingw64, mingw64-tools and ... well every other mingw
package I could
On 03/23/2014 07:36 PM, Scott Talbert wrote:
On Sun, 23 Mar 2014, Scott Talbert wrote:
OK, I checked in that Changelog, and the version number bump to start
preping
for release.
I was looking into MinGW... and uh, I think I'm missing something.
I installed mingw32, mingw64,
On 03/23/2014 09:21 PM, Phil Dibowitz wrote:
I think you can probably just do this instead:
./configure --host=i686-pc-mingw32
That works. What does mingw32-make do in Fedora? :)
Actually, that's a dumb question, it's probably just:
make CC=i586-mingw32msvc-gcc LD=i586-mingw32msvc-ld
or
On 03/23/2014 09:28 PM, Scott Talbert wrote:
./configure --host=i686-pc-mingw32
That works. What does mingw32-make do in Fedora? :)
Probably just try 'make'?
'make' can't find windows.h. Make with the right vars defined got me further.
And in case it wasn't clear, I do understand the linker
Nevermind, I figured it out. Changing the configure to ./configure
--host=i686-w64-mingw32 worked.
--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
Be
On Sun, 23 Mar 2014, Phil Dibowitz wrote:
./configure --host=i686-pc-mingw32
That works. What does mingw32-make do in Fedora? :)
Probably just try 'make'?
'make' can't find windows.h. Make with the right vars defined got me further.
And in case it wasn't clear, I do understand the linker
On 03/23/2014 09:35 PM, Scott Talbert wrote:
On Sun, 23 Mar 2014, Phil Dibowitz wrote:
./configure --host=i686-pc-mingw32
That works. What does mingw32-make do in Fedora? :)
Probably just try 'make'?
'make' can't find windows.h. Make with the right vars defined got me further.
And in
25 matches
Mail list logo
