On 2014-07-11 10:45-0700 Alan W. Irwin wrote:
> Once, smokegen has done its stuff, then those generated *.cpp files
> are processed using the following include directories:
> ${CMAKE_CURRENT_SOURCE_DIR}
> ${CMAKE_SOURCE_DIR}/include
> ${CMAKE_SOURCE_DIR}/lib/qsastime
> ${CMAKE_SOUR
On 2014-08-28 16:18-0700 phil rosenberg wrote:
> Hi Alan
> I found the same location in the file you specified between checking emails.
> I have been through and added the \" where appropriate to the various (rpath,
> compile, linker) flags. This allows me to compile, but I am getting linker
>
Hi Alan
I found the same location in the file you specified between checking emails. I
have been through and added the \" where appropriate to the various (rpath,
compile, linker) flags. This allows me to compile, but I am getting linker
errors in the examples, because the linker flags are endin
On 2014-08-28 13:05-0700 David MacMahon wrote:
> Hi, Alan,
>
> On Aug 28, 2014, at 12:35 PM, Alan W. Irwin wrote:
>
>> According to
>> http://sourceforge.net/p/forge/documentation/Files-Readme/ it may be
>> that all I would have to do was change the README name to README.md to
>> make the SF softw
On 2014-08-28 20:33+0100 Phil Rosenberg wrote:
> Hi Alan
> Given what you said I did a quick google for cmake paths spaces and
immediately found this post
http://stackoverflow.com/questions/9964775/using-cmakes-include-directories-command-with-white-spaces.
Seems the issue is the same there and i
Hi, Alan,
On Aug 28, 2014, at 12:35 PM, Alan W. Irwin wrote:
> According to
> http://sourceforge.net/p/forge/documentation/Files-Readme/ it may be
> that all I would have to do was change the README name to README.md to
> make the SF software translate that file from markdown to html, but
> then
On 2014-08-28 11:42-0700 David MacMahon wrote:
> Hi, Alan,
>
> On Aug 28, 2014, at 10:46 AM, Alan W. Irwin wrote:
>
>> On 2014-08-28 12:44-0400 Hazen Babcock wrote:
>>
>>> In the README file, should I be able to click on the links when viewed here?
>>> http://sourceforge.net/p/plplot/plplot/ci/mas
Hi Alan
Given what you said I did a quick google for cmake paths spaces and immediately
found this post
http://stackoverflow.com/questions/9964775/using-cmakes-include-directories-command-with-white-spaces.
Seems the issue is the same there and is a result of the find modules assuming
no whites
Hi, Alan,
On Aug 28, 2014, at 10:46 AM, Alan W. Irwin wrote:
> On 2014-08-28 12:44-0400 Hazen Babcock wrote:
>
>> In the README file, should I be able to click on the links when viewed here?
>> http://sourceforge.net/p/plplot/plplot/ci/master/tree/
>
> I don't think that is possible with plain
On 2014-08-28 10:06-0700 phil rosenberg wrote:
> Hi Alan
> I have done my best to look at this, but I am struggling. Looking at the
> various tcl related variables they all appear at first glance to be fine. I
> have just tried literally outputting every variable at the end of the top
> level c
On 2014-08-28 12:44-0400 Hazen Babcock wrote:
> On 8/28/2014 11:24 AM, Alan W. Irwin wrote:
>> My README and website changes have been pushed as of d5b1568, and the
>> corresponding changes to the website have been uploaded. Please take
>> a critical look at README and http://plplot.sourceforge.n
Hi Alan
I have done my best to look at this, but I am struggling. Looking at the
various tcl related variables they all appear at first glance to be fine. I
have just tried literally outputting every variable at the end of the top level
cmakelists.txt. Looking through I notices that the ntk_COMP
On 8/28/2014 11:24 AM, Alan W. Irwin wrote:
> On 2014-08-25 12:54-0700 Alan W. Irwin wrote:
>
>> On 2014-08-13 10:28-0400 Hazen Babcock wrote:
>>
>>> 1. Like github, SF is displaying the README.txt file. This appears to
>>> have last been modified in 2007. Maybe this should be the same as
>>> READM
On 2014-08-25 12:54-0700 Alan W. Irwin wrote:
> On 2014-08-13 10:28-0400 Hazen Babcock wrote:
>
>> 1. Like github, SF is displaying the README.txt file. This appears to
>> have last been modified in 2007. Maybe this should be the same as
>> README.release? Or maybe it should be updated?
>
> Thanks
On 8/27/2014 12:09 AM, Alan W. Irwin wrote:
> Here are some questions concerning git capabilities and
> our current workflow that you have documented in README.developers.
>
> Do you think it would be a good idea to change all the "git merge"
> commands in your workflow documentation to use the --f
15 matches
Mail list logo
