Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your
profile.
Okay so I'm a little puzzled why we have to include .mod files for every module used in a static .lib file when we want to hand the library over to someone else. Why do we have to do that? Why isn't the .lib file enough?
If the procedures are module procedures, then one needs the .mod file for the compiler to see the declaration of the procedure and know what its external name is. The .lib is used by the linker only.
If the procedures are module procedures, then one needs the .mod file for the compiler to see the declaration of the procedure and know what its external name is. The .lib is used by the linker only.
