Hi Nate:
Thank you for your comment. So, does that also mean that if I
include any of the file in the m5/src/ directory in the EXTRAS=foo/bar
file, I need to specify that file in the path that is relative to the
foo/bar directory?
Let's say that I have my foo/bar file in /home and m5/src is also in
home. So the path is
/home/m5/src
/home/foo/bar
For all my files in the foo/bar directory to include a simple.hh
file in the m5/src directory, I need to specify that
#include "../m5/src/simple.hh"
Is that right?
Thanks again for your comment.
Regards
James Wang
On Mon, Aug 3, 2009 at 4:08 PM, nathan binkert<[email protected]> wrote:
>> Hi Steve:
>> Thank you for your reply. The problem for my code to be outside of
>> the m5/src tree is that there are code in src/cpu/cpu_model.py that
>> has to
>> #include "cpu/timingtracecpu/timing_trace.hh"
>> If I put my code outside the m5/src/ how do I make sure the
>> cpu_model.py can still include the header file? Thank you again for
>> your comment.
>
> I believe that in this case, you're going to have to just edit that
> file. I've actually got code that removes that file as part of my
> sweeping changes to scons and tests, but it's probably a few weeks
> from being committed. (Basically there's a CPUModel directive in
> SCons now).
>
> The header file itself will have a path relative to the EXTRA
> directory that you provide.
>
> So if you have EXTRAS=foo/bar
> and you have a file called foo/bar/blah/baz.hh, you'll do
> #include "blah/baz.hh"
>
> Nate
>
--
Regards
James Wang
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
