Mountain Lion x64

[ntbosscher]

Using xcode I received the following error. I have the correct qt library installed and corrected folder location in build settings.

Thank for your work
Nate

[rdnelson]

What exactly is the error that you're getting?

[ntbosscher]

Did you look at the image attached to the bug report?

Undefined symbols for architecture x86_64:
"Instruction::InitializeOpcodes()", referenced from:
VM::VM() in VM.o
"QInstructionList::QInstructionList(QWidget_)", referenced from:
Ui_MemWnd::setupUi(QMainWindow_) in MemWnd.o
ld: symbol(s) not found for architecture x86_64

On 2013-09-17, at 2:58 PM, Robert Nelson notifications@github.com wrote:

What exactly is the error that you're getting?

—
Reply to this email directly or view it on GitHub.

[rdnelson]

I didn't see any attachments, so apologies for having to ask for the error message.

It's quite likely that the xcode project doesn't include some of the newer files (it was written quite a while ago.)

In this case, it appears that InstTable.cpp and QInstructionList.cpp are missing from the project.

I imagine that there will be a few more of these linker errors once this one is resolved. In most cases, the class name (the name before the :: at the beginning of the error) corresponds to the missing file.

If you can wait for a few days, we're currently migrating to a new build system that should generate a complete xcode project for you.

[ntbosscher]

Sounds good.
Also note that your build directories in Xcode are set to your personal ones, but should be relative to the Xcode project file.

Thanks
Nate

On 2013-09-17, at 4:14 PM, Robert Nelson notifications@github.com wrote:

I didn't see any attachments, so apologies for having to ask for the error message.

It's quite likely that the xcode project doesn't include some of the newer files (it was written quite a while ago.)

In this case, it appears that InstTable.cpp and QInstructionList.cpp are missing from the project.

I imagine that there will be a few more of these linker errors once this one is resolved. In most cases, the class name (the name before the :: at the beginning of the error) corresponds to the missing file.

If you can wait for a few days, we're currently migrating to a new build system that should generate a complete xcode project for you.

—
Reply to this email directly or view it on GitHub.