This probably doesn't directly help your issues here, but the SWIG 3.0
issue seems to have been fixed in SWIG 3.0.1 which was released yesterday.
http://sourceforge.net/p/swig/news/2014/05/swig-301-released/
- A few notable regressions introduced in 3.0.0 have been fixed - in
Lua, nested cla
Timothy,
I have not. I had family in town and was on vacation. I'm just getting back
to normalcy starting today, so I should have a chance to look in the near
future.
--Greg
On Wed, May 28, 2014 at 3:24 PM, R Johnson <
ps16thypresenceisfullnessof...@gmail.com> wrote:
> Greg,
>
> Have you had a
I now have gotten closer to being able to do what I want, but still not
quite there yet (sigh).
I tried to build the 'libsword' solution without the 'sword_static'
project, but then I actually got more errors than before. I have
attached the output I got.
I then tried building only the 'swor
Do you happen to know which of the projects in the solution failed to
build? I didn't try any of them outside of sword, swordswig, buildtest,
installmgr, and diatheke. All of those worked fine, although I did not test
the result of swordswig to see if it executed.
If you're building all of them, t
I now have the core library compiling through CMake with the following
invocation:
C:\Users\Gregory\Documents\building\sword-build>cmake ..\sword -G"Visual
Studio 12" -DBZIP2_LIBRARY=..\bzip2\Release\libbz2.lib
-DBZIP2_INCLUDE_DIR=..\bzip2 -DXZ_LIBRARY=..\xz\bin_i486\liblzma.lib
-DXZ_INCLUDE_DIR=.
On Tue, May 13, 2014 at 3:56 PM, Greg Hellings wrote:
>
>
>
> On Tue, May 13, 2014 at 3:48 PM, R Johnson <
> ps16thypresenceisfullnessof...@gmail.com> wrote:
>
>> Thanks, Greg and Ben.
>>
>>
> If we could get that working, it would be great! Unfortunately, I don't
>> have any experience with CMake
On Tue, May 13, 2014 at 3:48 PM, R Johnson <
ps16thypresenceisfullnessof...@gmail.com> wrote:
> Thanks, Greg and Ben.
>
>
If we could get that working, it would be great! Unfortunately, I don't
> have any experience with CMake either (in fact, I had never heard of it
> until I started trying to bu
Thanks, Greg and Ben.
> On the other hand, if you wish to keep on keeping on through the C#
project
> solution file you're more than welcome to do so, though. It's long out of
> date and unmaintained, so feel free to edit, hack, fix, and prod it
as much
> as you'd like. If you succeed in build
I think the key is here in your first email:
1>..\..\..\include\swbuf.h(362): error : Syntax error in input(3).
What is on the line it mentions? You may be missing a #define which matters.
It's possible no one has tested it with Swig 3.0 (I haven't built for a
while, but I used SWIG 1.3.31 last
Timothy,
I maintain the Python bindings, but we only officially support them through
Swig on Linux and other places and only really through the CMake build
project (and Troy also tries to keep them building through autotools as
well). And while there have been abortive attempts to get Swig C# bind
I just tried building this again with the new version of Sword (1.7.3)
and it still doesn't work.
I forgot to mention in my previous e-mail that I have added SWIG to my
PATH environment variable and set the PYTHON_INCLUDE and PYTHON_LIB
environment variables as required.
I have also attached
11 matches
Mail list logo