-
1. Re: PSoC Designer Build Error (ilibw.exe)
user_1377889 Oct 23, 2016 5:07 AM (in response to reddemkaran.reddy_1986216)Project compiles fine although requests update for ADCINC component.
When de-install and re-install of Designer does not help, I would suggest you to get in contact with Cypress directly: At top of this page select "Design support -> Create a Support Case" and ask your question. You will be helped by a Cypress engineer.
Bob -
2. Re: PSoC Designer Build Error (ilibw.exe)
chengjingjia_2029701 Nov 17, 2016 12:12 AM (in response to reddemkaran.reddy_1986216) -
3. Re: PSoC Designer Build Error (ilibw.exe)
user_1377889 Nov 17, 2016 12:23 AM (in response to reddemkaran.reddy_1986216)Welcome in the forum.
Did you read and follow my previous post?
Bob
-
4. Re: PSoC Designer Build Error (ilibw.exe)
reddemkaran.reddy_1986216 Nov 17, 2016 8:14 PM (in response to reddemkaran.reddy_1986216)1) Go to the below location (location might slightly vary on your PC based on your installation folder of PSoC Designer):
C:\Program Files (x86)\Cypress\PSoC Designer\5.4\Common\CypressSemiBuildMgr\tools
2) Right-click on "ilibw.exe" and click on "Properties" and then go to "Compatibility" tab, and check the "Run this program in compatibility mode for" checkbox, and in the drop-down, select "Windows 7".
3) Open PSoC Designer and the project, and try building, and check if the issue is overcome.
If the issue still persists, repeat the same procedure, but instead of "Windows 7" select "Window XP (Service Pack 3)" in the compatibility drop-down.
This did not work for me, instead it threw a new error. Maybe you can try this solution and let me know if it worked for you.
-
5. Re: PSoC Designer Build Error (ilibw.exe)
reddemkaran.reddy_1986216 Nov 17, 2016 8:18 PM (in response to reddemkaran.reddy_1986216)An alternate solution is starting windows in safe mode and building the application. Although, it is tedious, it is the only workaround I have found to this problem till now.
-
6. Re: PSoC Designer Build Error (ilibw.exe)
k.k.2 Nov 26, 2016 5:14 AM (in response to reddemkaran.reddy_1986216)This problem will be resolved by uninstalling the "symantec" product.