Access path

Access path

Post by F.C. Kuechman » Sat, 16 Nov 2002 19:34:33



I'm updating CWPro 5.3 to Universal Interfaces 3.4.1 in order to do
Carbon dev on a PM8500/180 W/MacOS-8.6. The install instructions say to
add MSL to the "access path" & re-compile MacHeaders [& others,
preesumably including the Pascal stuff]. What,  exactly, does that
mean?

Cheerz

 
 
 

Access path

Post by MW Ro » Sun, 17 Nov 2002 07:05:09




Quote:>I'm updating CWPro 5.3 to Universal Interfaces 3.4.1 in order to do
>Carbon dev on a PM8500/180 W/MacOS-8.6. The install instructions say to
>add MSL to the "access path" & re-compile MacHeaders [& others,
>preesumably including the Pascal stuff]. What,  exactly, does that
>mean?

with the CodeWarrior pascal patch there is a project the rebuilds the
Pascal Libraries.   you need to add a path to the MSL folder for that
project and then rebuild them.

Simple as that.

Ron

--
        Can you really afford not to use CodeWarrior 8.3 ?
Faster compiles, Improve Code Generation, Updated IDE for OS X 10.2
    http://metrowerks.com/MW/Support/Download/default.htm



 
 
 

Access path

Post by F.C. Kuechman » Mon, 18 Nov 2002 07:17:21






> >I'm updating CWPro 5.3 to Universal Interfaces 3.4.1 in order to do
> >Carbon dev on a PM8500/180 W/MacOS-8.6. The install instructions say to
> >add MSL to the "access path" & re-compile MacHeaders [& others,
> >preesumably including the Pascal stuff]. What,  exactly, does that
> >mean?

> with the CodeWarrior pascal patch there is a project the rebuilds the
> Pascal Libraries.   you need to add a path to the MSL folder for that
> project and then rebuild them.

> Simple as that.

> Ron

 Maybe I'm getting old or something, but the only "Access path"
settings I can find are in the project settings dialog accessed
via the Edit menu. There are two panes --

User paths
   {Project}:

System paths
   {Compiler}

---------

I tried this to put MSL in the user path

User paths
   {Project}:
   {Project}::MSL:

But still get the same compile errors. The only Access path stuff I
can find in the dox is no help.

An actual step-by-step example of adding MSL to a specific project's
access path would be most helpful. Say, the project MacHeaders.mcp or
MSL_Pascal.PPC.Mtarg.mcp

 
 
 

Access path

Post by Sean McBrid » Mon, 18 Nov 2002 10:46:51




Quote:> I tried this to put MSL in the user path

> User paths
>    {Project}:
>    {Project}::MSL:

MSL should be in the system, not user path.  And it should be a
'compliler' relative path.
 
 
 

Access path

Post by F.C. Kuechman » Tue, 19 Nov 2002 05:34:10






> > I tried this to put MSL in the user path

> > User paths
> >    {Project}:
> >    {Project}::MSL:

> MSL should be in the system, not user path.  And it should be a
> 'compliler' relative path.

Eurika! I got MacHeaders to compile. MSL had to be added to the access
path of each target -- 68k, 68k-CFM and PPC. Adding to Build All
doesn't do it.

With MSL_Pascal.PPC.Mtarg.mcp, I get still these errors with targets
Rt PPC TOOL (opt.) and Rt PPC TOOL (dbg.) --

Error   : illegal function definition
wcstoul.h line 33   wint_t

extern unsigned long    __wcstoul(  int   base,
                              int      max_width,
            ----->         __std(wint_t) (*ReadProc)(void *,
__std(wint_t), int),   /* mm 990326, hh 990507 */
                              void * ReadProcArg, /* mm 990326 */
                              int   * chars_scanned,
                              int   * negative,
                              int   * overflow);

Error   : illegal function definition
wcstoul.h line 42   wint_t

#ifdef __MSL_LONGLONG_SUPPORT__              /*mm 970110*/
extern unsigned long long  __wcstoull( int   base,
                              int      max_width,
            ------->    __std(wint_t) (*ReadProc)(void *,
__std(wint_t), int),   /* mm 990326, hh 990507 */
                              void * ReadProcArg,     /* mm 990326 */
                              int   * chars_scanned,
                              int   * negative,
                              int   * overflow);
#endif   /*__MSL_LONGLONG_SUPPORT__*/        /*mm 970110*/

 
 
 

Access path

Post by MW Ro » Wed, 20 Nov 2002 04:28:55




Quote:>With MSL_Pascal.PPC.Mtarg.mcp, I get still these errors with targets
>Rt PPC TOOL (opt.) and Rt PPC TOOL (dbg.) --

You should not have this targets, just remove them.  This is for MPW
libraries.

Ron

--
        Can you really afford not to use CodeWarrior 8.3 ?
Faster compiles, Improve Code Generation, Updated IDE for OS X 10.2
    http://metrowerks.com/MW/Support/Download/default.htm


 
 
 

1. Access Paths

For some reason, even though I have my include directories set up correctly in
the Access Paths panel, the compiler tells me it can't find a header file in
that path.  What is the logic behind the way the access paths are searched for
include files?

When adding an access path, why are not all options available in the "Relative
To" drop down box?  Sometimes "Project", "CodeWarrior", and "System" are not
available.

Thanks,

Brian

2. who's out here?

3. access paths

4. Hardware Malfunction - System Halted

5. OS X command line precompiler access paths

6. 2000 $sex-WebSites FREE

7. Access path not found under OSX

8. Little question reguarding firewall conflicts

9. Changing access paths with COM automation (CW7.0)

10. access paths

11. Access Paths in Java IDE

12. sas on unix accessing nt files using unc path

13. How to access DBF's with UNC path on NT server