Csound Csound-dev Csound-tekno Search About

[Csnd] include dir question

Date2018-12-03 13:16
FromOeyvind Brandtsegg
Subject[Csnd] include dir question
It might seem like an oddity regarding the include dir happening in recent versions of Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 13:26
FromOeyvind Brandtsegg
SubjectRe: [Csnd] include dir question
... and actually using --env:INCDIR= does not appear to change things either, ther terminal still prints the same
...
using path .
setting path from . to inc
using path inc
...


Den man. 3. des. 2018 kl. 14:16 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
It might seem like an oddity regarding the include dir happening in recent versions of Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 13:35
FromJohn ff
SubjectRe: [Csnd] include dir question
Yes this was changed as there were complaints that C changed the root for nested includes.

Check the issues

Sent from TypeApp
On 3 Dec 2018, at 13:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote
It might seem like an oddity regarding the include dir happening in recent versions of  Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 13:39
FromOeyvind Brandtsegg
SubjectRe: [Csnd] include dir question
Thank you.
but now it seems it does actually change the root for nested includes.
If I use the code (as mentioned in my original post)

#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

Then I have to put the file ftables_envelopes.inc in /inc/inc so that it is found.
I was expecting to be able to put it in /inc, not in /inc/inc


Den man. 3. des. 2018 kl. 14:35 skrev John ff <jpff@codemist.co.uk>:
Yes this was changed as there were complaints that C changed the root for nested includes.

Check the issues

Sent from TypeApp
On 3 Dec 2018, at 13:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote
It might seem like an oddity regarding the include dir happening in recent versions of  Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 13:58
FromOeyvind Brandtsegg
SubjectRe: [Csnd] include dir question
I did check the issues discussion from June now, and see that I was missing out from this discussion.
I think it is a grave problem that we implement changes that are not backwards comtatible. One of Csound\s strongest points is the backwards compatibility. And this is not kept when such changes are made. I also see in the discussion that there was indeed a discussion about if this was the correct way to go.
I am very much opposed to changes that break backwards compatibility. It does destroy older orchestras!
If someone other than the author attempts to run these orchestras they will have severe difficulties untangling these issues.


Den man. 3. des. 2018 kl. 14:39 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
Thank you.
but now it seems it does actually change the root for nested includes.
If I use the code (as mentioned in my original post)

#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

Then I have to put the file ftables_envelopes.inc in /inc/inc so that it is found.
I was expecting to be able to put it in /inc, not in /inc/inc


Den man. 3. des. 2018 kl. 14:35 skrev John ff <jpff@codemist.co.uk>:
Yes this was changed as there were complaints that C changed the root for nested includes.

Check the issues

Sent from TypeApp
On 3 Dec 2018, at 13:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote
It might seem like an oddity regarding the include dir happening in recent versions of  Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here


--


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 14:00
FromOeyvind Brandtsegg
SubjectRe: [Csnd] include dir question
... discussion was from July to Oct, not in June as I said. Link here>

Den man. 3. des. 2018 kl. 14:58 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
I did check the issues discussion from June now, and see that I was missing out from this discussion.
I think it is a grave problem that we implement changes that are not backwards comtatible. One of Csound\s strongest points is the backwards compatibility. And this is not kept when such changes are made. I also see in the discussion that there was indeed a discussion about if this was the correct way to go.
I am very much opposed to changes that break backwards compatibility. It does destroy older orchestras!
If someone other than the author attempts to run these orchestras they will have severe difficulties untangling these issues.


Den man. 3. des. 2018 kl. 14:39 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
Thank you.
but now it seems it does actually change the root for nested includes.
If I use the code (as mentioned in my original post)

#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

Then I have to put the file ftables_envelopes.inc in /inc/inc so that it is found.
I was expecting to be able to put it in /inc, not in /inc/inc


Den man. 3. des. 2018 kl. 14:35 skrev John ff <jpff@codemist.co.uk>:
Yes this was changed as there were complaints that C changed the root for nested includes.

Check the issues

Sent from TypeApp
On 3 Dec 2018, at 13:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote
It might seem like an oddity regarding the include dir happening in recent versions of  Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here


--


--


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2018-12-03 17:25
FromOeyvind Brandtsegg
SubjectRe: [Csnd] include dir question
I replied to the discussion on the issue 973 now, to keep it all in one place.



Den man. 3. des. 2018 kl. 15:00 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
... discussion was from July to Oct, not in June as I said. Link here>

Den man. 3. des. 2018 kl. 14:58 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
I did check the issues discussion from June now, and see that I was missing out from this discussion.
I think it is a grave problem that we implement changes that are not backwards comtatible. One of Csound\s strongest points is the backwards compatibility. And this is not kept when such changes are made. I also see in the discussion that there was indeed a discussion about if this was the correct way to go.
I am very much opposed to changes that break backwards compatibility. It does destroy older orchestras!
If someone other than the author attempts to run these orchestras they will have severe difficulties untangling these issues.


Den man. 3. des. 2018 kl. 14:39 skrev Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no>:
Thank you.
but now it seems it does actually change the root for nested includes.
If I use the code (as mentioned in my original post)

#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

Then I have to put the file ftables_envelopes.inc in /inc/inc so that it is found.
I was expecting to be able to put it in /inc, not in /inc/inc


Den man. 3. des. 2018 kl. 14:35 skrev John ff <jpff@codemist.co.uk>:
Yes this was changed as there were complaints that C changed the root for nested includes.

Check the issues

Sent from TypeApp
On 3 Dec 2018, at 13:17, Oeyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote
It might seem like an oddity regarding the include dir happening in recent versions of  Csound. 

I keep all include files in a separate directory underneath the directory where the csd is located.

In the csd file I have
#include "inc/globals_ftables.inc"
and in this file, I have 
#include "inc/ftables_envelopes.inc"

This used to work, being interpreted as relative paths. That is, relative to the csd. Now it looks like the path is being updated when I include the first file, so that the path is then relative to the /inc dir.

The terminal prints this:

using path .
setting path from . to inc
using path inc
Cannot open #include'd file inc/fofVoice_ftables.inc

Does this sound recognizable? any changes relating to path, relative path, include dir or so recently? (recently meaning 6-7 months ...).

best
Oeyvind


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here


--


--


--


--
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here