linker

问题 I was looking in the jam files, how the name of library is constructed. Example: libboost_log-mgw46-mt-1_48.dll I would like to ignore the last part, how to pass linker the -o parameter with my constructed name. I have few versions and linking in a big project forces me to do changes in project file and that is a lot of places. My wish is to get libboost_log.dll. I did just rename, but when executing a program it says, that it can not find libboost_log-mgw46-mt-1_48.dll file. 回答1: Boost Bjam

问题 I was looking in the jam files, how the name of library is constructed. Example: libboost_log-mgw46-mt-1_48.dll I would like to ignore the last part, how to pass linker the -o parameter with my constructed name. I have few versions and linking in a big project forces me to do changes in project file and that is a lot of places. My wish is to get libboost_log.dll. I did just rename, but when executing a program it says, that it can not find libboost_log-mgw46-mt-1_48.dll file. 回答1: Boost Bjam

问题 All texts on how to create a compiler stop after explaining lexers and parsers. They don't explain how to create the machine code. I want to understand the end-to-end process. Currently what I understand is that, the Windows exe file formats are called Portable Executable. I read about the headers it has and am yet to find a resource which explains this easily. My next issue is, I don't see any resource which explains how machine code is stored in the file. Is it like 32-bit fixed length

问题 I am writing a little bootsector for learning purpose. Here is boot.S .code16 .text movw $0xB800, %ax /* 0xB000 is the text screen video memory */ movw %ax, %es /* set it as the %es segment */ movb label, %al movb %al, %es:0x0 /* screen[0] = 'A' */ movb $0x07, %es:0x1 /* white on black */ jmp . label: .byte 'A .=510 .byte 0x55 .byte 0xAA and here is the Makefile I use to compile it to a raw binary file hdd.img: boot.S as $< -o boot.o ld --oformat binary -Ttext 0x7c00 boot.o -o hdd.img I face

问题 I am trying to compile my TBB program using MinGW. I know that TBB is installed on my machine correctly because it compiles just fine in Visual Studio. Do I have to do something more to tell MinGW where TBB is installed? Or is just linking the library all that is needed? I am getting these error, when trying to compile using gcc. C:\Users\Owner\Desktop\New folder\OpenMP vs TBB>make g++ -LC:\tbb\tbb\lib\intel64\vc14 -O3 -o pps avl.o main.o parPlaneSweep.o -fopenmp -ltbb c:/mingw/bin/../lib/gcc

问题 I would like to create a single library from objects from multiple sub-directories, each one containing their own CMakeLists.txt with OBJECT library trick to have multiple targets with different compile options. Here are the files: project_dir |--- subdir1 | |--- src1.c | |--- CMakeLists.txt |--- subdir2 | |--- src2.c | |--- CMakeLists.txt |--- CMakeLists.txt Contents of all CMakeLists.txt // project_dir/CMakeLists.txt // what to put here? to make one single library (mainLib) // project_dir

问题 I have the arm-none-linux-gnueabi-g++ compiler in the below path, root@user-VirtualBox:~# which arm-none-linux-gnueabi-g++ /home/user/octane_etk-6.0.0.240/arm-toolchain/bin/arm-none-linux-gnueabi-g++ and I have given the same in DCMAKE_COMPILER path in the build command of paho, user@user-VirtualBox:~/octane_etk_sample-6.0.0.240/paho.mqtt.c$ cmake -Bbuild -H. -DPAHO_WITH_SSL=OFF -DPAHO_ENABLE_TESTING=OFF -DCMAKE_C_COMPILER=/home/user/octane_etk-6.0.0.240/arm-toolchain/bin/arm-none-linux

问题 I'm in a situation that's quite similar to the following. There's libA.so that depending on some compile time flags exhibits slightly different behaviour (it's an external lib, and I can't modify the source). Then, I have libB.so that depends on libA.so (compiled with say -DVALUE=1 ), and in my executable I depend both on libB.so , as well as on libA.so , but compiled with -DVALUE=0 . However, once I launch it, ld resolves all symbols with one of libA.so versions, so both my executable and

问题 I'm in a situation that's quite similar to the following. There's libA.so that depending on some compile time flags exhibits slightly different behaviour (it's an external lib, and I can't modify the source). Then, I have libB.so that depends on libA.so (compiled with say -DVALUE=1 ), and in my executable I depend both on libB.so , as well as on libA.so , but compiled with -DVALUE=0 . However, once I launch it, ld resolves all symbols with one of libA.so versions, so both my executable and

问题 I'm in a situation that's quite similar to the following. There's libA.so that depending on some compile time flags exhibits slightly different behaviour (it's an external lib, and I can't modify the source). Then, I have libB.so that depends on libA.so (compiled with say -DVALUE=1 ), and in my executable I depend both on libB.so , as well as on libA.so , but compiled with -DVALUE=0 . However, once I launch it, ld resolves all symbols with one of libA.so versions, so both my executable and