X C-Hook Question

[Bullines]

I'm updating one of my v9.x C-Hooks for X and have run into a problem.

 

I need to get a list of Lathe tools in the current file and back in v9.x, I did so like this:

 

code:

---

void *pVoidLtl = NULL;

tl_list *pLtl = NULL, *pCurLtl;

char szLibName[255] ="";

 

 

// Get the linked list of tools.

list_manager(LTL_ID, szLibName, LSTMGR_GET, &pVoidLtl);

 

// Get the head of the list.

pLtl = (ltl_list *)pVoidLtl;

 

// As long as the list isn't empty, iterate

// through each tool in the list and do

// some super kewl stuff.

if (pLtl != NULL)

{

// Set the current pointer to the head of the

// tool list.

pCurLtl = pLtl;

 

// Iterate through the list of tools.

while (pCurLtl != NULL)

{

// do some super kewl stuff

// do more super kewl stuff

 

// get next tool

pCurLtl = pCurLtl->next_ptr;

}

}

 

// free up the allocated linked list

list_manager(LTL_ID, szLibName, LSTMGR_FREE, &pVoidLtl);

---

This code compiles fine for X but it doesn't build. The linker hates list_manager() and returns a 2019 error (unresolved external symbol). I've tried using different ids (TL_ID instead of LTL_ID) and casting the list pointer earlier:

 

code:

---

list_manager(TL_ID, szLibName, LSTMGR_GET, (void**)&pLtl);

---

But the result is the same.

 

Any suggestions?

[kinglouie V]

you know way more than me dude, but I did run into a problem that I thought was curious. I have a custom tool file .tl9 that wouldn't import AT ALL. So I converted to text and then imported fine. Can you do something like that to get it to build in X?

[Bullines]

quote:

---

Can you do something like that to get it to build in X?

---

If only software development worked like that

[Steve Benson from CNC Software]

Are you linking to mcmill.lib?

[Jon Griffin CNC Software]

Bullines,

 

That sort of error almost always comes up when building a new chook. It's because you aren't linking properly to the .lib files (as Steve is pointing out). You've probably forgotten one.

Assuming that you're using Visual Studio, you need to also remember to include the debug and release versions of the libs, and to exclude them from the opposite builds (ie. release from debug and vice versa).

Had this happen to me a few times.

 

Jon

[Bullines]

Steve and Jon (and Bob, who was absent in this thread but was there via email and phone),

 

Big-time thanks

 

I was linking to mastercam.lib and mccore.lib but not mcmill.lib. I guess I was lazy and thought the C-Hook Wizard would take care of it all (I must've flew through that dialog). I'm continuously noticing how much the SDK has changed from previous versions

 

Now the joy of testing begins...