Compilation works with the current CMake version.
Regards,
Daniel
Am Do., 11. Feb. 2021 um 11:48 Uhr schrieb Daniel Roßberg <
danielmrossb...@gmail.com>:
> Confirmed.
>
> The set_property() statements are a bit different in this CMakeLists.txt
> file: APPEND vs. APPEND_STRING
> "If the APPEN
Confirmed.
The set_property() statements are a bit different in this CMakeLists.txt
file: APPEND vs. APPEND_STRING
"If the APPEND option is given the list is appended to any existing
property value (except that empty values are ignored and not appended). If
the APPEND_STRING option is given the st
So, to confirm you're seeing the line:
32.2/include";CFG_RUNTIME_DOCDIR="C:/Program Files/BRL-CAD
7.32.2/share/man"-Ot -Oi
Checking my output, it looks like:
32.2/include";CFG_RUNTIME_DOCDIR="C:/Program Files/BRL-CAD
7.32.2/share/man";-Ot -Oi
Those flags are coming from this line (src/other/tcl
Yes, clean checkout and new created build directory. CMake version is
3.15.4.
The bug is visible in the tcl.vcxproj file: In the lines containing
CFG_RUNTIME_DOCDIR, a semicolon is missing after the directory string. If
you have it with your version, I'll try again with an updated CMake.
(Unfortun
Is that with a clean build directory? Also, which version of CMake?
I also built with VS2019, so it's curious that that configuration should
fail...
On Tue, Feb 9, 2021 at 10:44 AM Daniel Roßberg
wrote:
> Hmm, my Visual Studio 2019 build fails, Release, sources from
> branches/RELEASE, plain
Hmm, my Visual Studio 2019 build fails, Release, sources from
branches/RELEASE, plain CMake run (nothing changed).
Error in src/other/tcl/generic/tclPkgConfig.c, line 107. The
CFG_RUNTIME_DOCDIR makro looks bad. It includes compiler switches after
the path string. They aren't cleanly separated (
On Jun 24, 2012, at 1:18 PM, Tom Browder wrote:
> On Sun, Jun 24, 2012 at 9:48 AM, Christopher Sean Morrison
> wrote:
>> Release preparations have begun (again). Please refrain from disruptive
>> commits until the
>
> Oops, sorry, just saw this.
Doc edits aren't disruptive. No worries.
Che
On Sun, Jun 24, 2012 at 9:48 AM, Christopher Sean Morrison
wrote:
> Release preparations have begun (again). Please refrain from disruptive
> commits until the
Oops, sorry, just saw this.
-Tom
--
Live Security Virtual
I
- opened a command line
- started bwish.exe
- loaded archer
=> a short splash screen, that's all
bwish releases the console automatically on start-up as usual among MS
Windows programs.
However, if I compile it with the Debug settings I see no splash
screen but a R6034 runtime error on loading a
On Jun 15, 2012, at 10:03 AM, Daniel Roßberg wrote:
> 2012/6/15 Christopher Sean Morrison :
>>
>> On Jun 15, 2012, at 8:13 AM, Daniel Roßberg wrote:
>>> - archer refused to work on x64
>>
>> Huh, odd. Bob is working on an issue in archer today (which is technically
>> what we're waiting on)
2012/6/15 Christopher Sean Morrison :
>
> On Jun 15, 2012, at 8:13 AM, Daniel Roßberg wrote:
>> - archer refused to work on x64
>
> Huh, odd. Bob is working on an issue in archer today (which is technically
> what we're waiting on), but starting archer isn't the issue. Does it display
> any e
On Jun 15, 2012, at 8:13 AM, Daniel Roßberg wrote:
> The current status on Windows with MSVS is:
>
> - INSTALL and brlcad can be build on both win32 and x64
> - archer and mged can be started on win32 (opened a database and
> made a ray-trace)
> - mged can be started on x64 (opened a datab
The current status on Windows with MSVS is:
- INSTALL and brlcad can be build on both win32 and x64
- archer and mged can be started on win32 (opened a database and
made a ray-trace)
- mged can be started on x64 (opened a database and made a ray-trace)
- archer refused to work on x64
On Jun 15, 2012, at 2:12 AM, Daniel Roßberg wrote:
> There was a problem with the mailing list again. I send my mail
> yesterday morning (see at the date and time). It referred to r51119.
> See r51129 for my changes.
Yeah, I noticed that too. It looked like the devel and commit messages were
There was a problem with the mailing list again. I send my mail
yesterday morning (see at the date and time). It referred to r51119.
See r51129 for my changes.
Daniel
2012/6/15 Christopher Sean Morrison :
>
> On Jun 14, 2012, at 9:37 AM, Daniel Roßberg wrote:
>
>> No. Error in line 56 ...
>
>
On Jun 14, 2012, at 9:37 AM, Daniel Roßberg wrote:
> No. Error in line 56 ...
That's a blank line for me.. maybe update conflict? What's the error?
The netinet/in.h header is for htons() which windows provides in winsock2.h
(which bin.h should be including).
Cheers!
Sean
--
No. Error in line 56 ...
Daniel
2012/6/14 Christopher Sean Morrison :
>
>
> On Jun 14, 2012, at 4:25 AM, Daniel Roßberg wrote:
>
>> I'm getting a build error with MS Visual Studio: the include
>> "arpa/inet.h" is missing in "src/conv/asc/asc2dsp.c".
>
> Replaced with bin.h, better?
>
> Cheers!
>
On Thu, Jun 14, 2012 at 9:46 AM, brlcad wrote:
>
> On Jun 14, 2012, at 08:49 AM, Tom Browder wrote:
>
> On Wed, Jun 13, 2012 at 10:25 PM, Christopher Sean Morrison
> wrote:
>> Release preparations have begun. Please refrain from disruptive commits
>> until the release is tagged or
>
> Is it too
On Jun 14, 2012, at 08:49 AM, Tom Browder wrote:On Wed, Jun 13, 2012 at 10:25 PM, Christopher Sean Morrison
wrote:
> Release preparations have begun. Please refrain from disruptive commits until the release is tagged or
Is it too late to add a new regression test for asc2dsp? I
On Wed, Jun 13, 2012 at 10:25 PM, Christopher Sean Morrison
wrote:
> Release preparations have begun. Please refrain from disruptive commits
> until the release is tagged or
Is it too late to add a new regression test for asc2dsp? It'll take a
few minutes.
Best,
-Tom
---
On Jun 14, 2012, at 4:25 AM, Daniel Roßberg wrote:
> I'm getting a build error with MS Visual Studio: the include
> "arpa/inet.h" is missing in "src/conv/asc/asc2dsp.c".
Replaced with bin.h, better?
Cheers!
Sean
--
L
I'm getting a build error with MS Visual Studio: the include
"arpa/inet.h" is missing in "src/conv/asc/asc2dsp.c".
Daniel
2012/6/14 Christopher Sean Morrison :
> Release preparations have begun. Please refrain from disruptive commits
> until the release is tagged or 24-hours have passed, which
22 matches
Mail list logo