New package for Windows is available for download on my website
www.freddiechopin.info
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On 2011-10-20 01:42, Peter Stuge wrote:
Maybe you can also describe how you build them?
No magic here - it's just much simpler to do crosscompilation on Linux
than fighting natively in Windows. The cause of problems in Windows is
that OpenOCD needs many tools to be compiled. libftdi needs eve
Hi!
I've prepared a package but I've found "an inconvenience" in handling
paths in new version (see other thread) so I'll see whether there's a
will and possibility to fix/change that before publishing. If you need
it now I can send you the package.
4\/3!!
___
On Thu, Oct 20, 2011 at 7:42 AM, Peter Stuge wrote:
> Freddie Chopin wrote:
>> I guess it's right time for me to provide a new development version
>> on my website...
>
> Maybe you can also describe how you build them?
>
Freddie does provide a simple description about the build
in his package.
+
Freddie Chopin wrote:
> I guess it's right time for me to provide a new development version
> on my website...
Maybe you can also describe how you build them?
//Peter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lis
On 2011-10-19 16:22, Attila Kinali wrote:
Could someone give me a pointer on how to build current git HEAD on windows?
None of the howtos on the net i've tried worked. Each and everyone
failed at some point with errors that are out of my league (linking
errors, libtool errors etc).
Alternatively
Attila Kinali wrote:
> Could someone give me a pointer on how to build current git HEAD on windows?
> None of the howtos on the net i've tried worked. Each and everyone
> failed at some point with errors that are out of my league (linking
> errors, libtool errors etc).
Post the actual errors and y
