Laurent Gauch wrote:
>> >/ we have to make sure the compile step stays as easy as possible on
>> />/ Windows as on Linux and Mac !
>> /
>> I don't agree. Windows is pretty much a useless development
>> environment as-is,
>
> That's your point of view ... but, for me, this is a user point of
> vie
Laurent Gauch wrote:
>/ Having external Jim TCL is not so bad,
/
I think it's an important improvement.
>/ we have to make sure the compile step stays as easy as possible on
/>/ Windows as on Linux and Mac !
/
I don't agree. Windows is pretty much a useless development
environment as-is,
That'
Laurent Gauch wrote:
> Having external Jim TCL is not so bad,
I think it's an important improvement.
> we have to make sure the compile step stays as easy as possible on
> Windows as on Linux and Mac !
I don't agree. Windows is pretty much a useless development
environment as-is, and it's not r
Spencer Oliver wrote:
> The issue is caused because jim will install into /usr/local/lib.
> cygwin and mingw will only look in /usr/lib - quick solution is to
> manually move the various files.
Quick but note that it is also a dirty solution, since you are not
only circumventing the packaging syst
Øyvind Harboe wrote:
Yes, but having jim as standalone make a new dependency for openocd project
:-( ! With new version control of jim TCL ...
The current thinking is to have the choice of whether
to use installed Jim Tcl or have OpenOCD just build the Jim
Tcl that ships with(submodule) Op
> Yes, but having jim as standalone make a new dependency for openocd project
> :-( ! With new version control of jim TCL ...
The current thinking is to have the choice of whether
to use installed Jim Tcl or have OpenOCD just build the Jim
Tcl that ships with(submodule) OpenOCD.
Release builds ar
>/ I think we do not need to have any 'make install' for JIM TCL,
/>/ since we want JIM TCL embedded in the openocd project.
/
As you may already know, if a project uses autotools then the build
is not completed without make install.
I would suggest to set --prefix for jim to a subdir of the ope
On 02/11/2010 12:55, Laurent Gauch wrote:
>/ won't it be better compile both jimtcl and openocd with single
/>/ ./configure and make, without needing to install that stuff
/>/ separatelly ?
/
It doesn't need to be installed, that's part of the point.
Although I'm thinking about if it might make
On Nov 3, 2010, at 11:13, Peter Stuge wrote:
> It could assume that jim was built and installed into some default
> prefix, but really, since jim is standalone, it would make sense to
> me to have it installed separately in the system even if it is linked
> statically into openocd.
Look at how GC
Laurent Gauch wrote:
> I think we do not need to have any 'make install' for JIM TCL,
> since we want JIM TCL embedded in the openocd project.
As you may already know, if a project uses autotools then the build
is not completed without make install.
I would suggest to set --prefix for jim to a su
Hi Steve,
Yes, you're right.
I think we do not need to have any 'make install' for JIM TCL, since we
want JIM TCL embedded in the openocd project.
The jim include paths and jim lib paths directly should be added in the
'configure' of openocd.
Regards,
Laurent
http://www.amontec.com
USB J
On 03/11/2010, at 8:34 AM, Steve Bennett wrote:
> On 03/11/2010, at 12:23 AM, Laurent Gauch wrote:
>
>> under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make error
>> is :
>>
>> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
>
> Did you forget 'make insta
On 03/11/2010, at 12:23 AM, Laurent Gauch wrote:
> under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make error
> is :
>
> ../../../src/helper/command.h:34:17: jim.h: No such file or directory
Did you forget 'make install' in ./openocd/jimtcl?
This is the symptom I see when that
under Cygwin with external JIM TCL 0.63 in ./openocd/jimtcl, the make
error is :
../../../src/helper/command.h:34:17: jim.h: No such file or directory
checking whether standard drivers can be built... yes
checking for ftd2xx.lib exists (win32)... checking whether ftd2xx
library works.
.. Suc
Laurent Gauch wrote:
> OpenOCD community will receive a lot of new messages regarding
> compilation errors / troubles, if we do not give any how-to compile
> with external JIM TCL.
Please contribute documentation.
//Peter
___
Openocd-development maili
>/ won't it be better compile both jimtcl and openocd with single
/>/ ./configure and make, without needing to install that stuff
/>/ separatelly ?
/
It doesn't need to be installed, that's part of the point.
Although I'm thinking about if it might make sense to package it
anyway. I guess it's l
As a side not the current "make install" will not install to the correct
dirs, so using AC_CONFIG_SUBDIRS solves all this.
I mean under windoze install :)
Cheers
Spen
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https:/
On 01/11/2010 00:48, Marek Vasut wrote:
On Sunday 31 October 2010 18:37:33 Øyvind Harboe wrote:
On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge wrote:
Øyvind Harboe wrote:
Is there also an upstream for Jim Tcl to make distribution packages
from?
Or is Jim Tcl only ever statically linked with Op
On Monday 01 November 2010 01:50:19 Peter Stuge wrote:
> Marek Vasut wrote:
> > won't it be better compile both jimtcl and openocd with single
> > ./configure and make, without needing to install that stuff
> > separatelly ?
>
> It doesn't need to be installed, that's part of the point.
In my cas
Marek Vasut wrote:
> won't it be better compile both jimtcl and openocd with single
> ./configure and make, without needing to install that stuff
> separatelly ?
It doesn't need to be installed, that's part of the point.
Although I'm thinking about if it might make sense to package it
anyway. I g
On Sunday 31 October 2010 18:37:33 Øyvind Harboe wrote:
> On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge wrote:
> > Øyvind Harboe wrote:
> >> > Is there also an upstream for Jim Tcl to make distribution packages
> >> > from?
> >> >
> >> > Or is Jim Tcl only ever statically linked with OpenOCD?
> >>
On Sun, Oct 31, 2010 at 6:26 PM, Peter Stuge wrote:
> Øyvind Harboe wrote:
>> > Is there also an upstream for Jim Tcl to make distribution packages
>> > from?
>> >
>> > Or is Jim Tcl only ever statically linked with OpenOCD?
>>
>> Statically linked, no change there.
>
> Ok. Has Jim Tcl ever been p
Øyvind Harboe wrote:
> > Is there also an upstream for Jim Tcl to make distribution packages
> > from?
> >
> > Or is Jim Tcl only ever statically linked with OpenOCD?
>
> Statically linked, no change there.
Ok. Has Jim Tcl ever been packaged independently? Is it "our" project
as well?
//Peter
_
On Sun, Oct 31, 2010 at 5:53 PM, Peter Stuge wrote:
> Øyvind Harboe wrote:
>> OpenOCD master branch now uses Jim Tcl.
>>
>> This means you'll have to build Jim Tcl before building OpenOCD.
>
> Is there also an upstream for Jim Tcl to make distribution packages
> from?
>
> Or is Jim Tcl only ever s
Øyvind Harboe wrote:
> OpenOCD master branch now uses Jim Tcl.
>
> This means you'll have to build Jim Tcl before building OpenOCD.
Is there also an upstream for Jim Tcl to make distribution packages
from?
Or is Jim Tcl only ever statically linked with OpenOCD?
//Peter
OpenOCD master branch now uses Jim Tcl.
This means you'll have to build Jim Tcl before building OpenOCD.
bootstrap prints the instructions:
git submodule init
git submodule update
cd jimtcl
./configure --with-jim-ext=nvp
make
make install
From the OpenOCD command line you can determine
the ver
26 matches
Mail list logo
