error after .aar integration - build

I was using .andlib upto now and now as CN1 has changed default to Gradle so in accordance to that I generated .aar of my native android code.
But when I had sent a build,
1) first I got duplicate permission error for Internet connection.
then I removed Internet Connection from my android project and it resolve error but
2) second time I got
Unknown source file : /tmp/build5662507870470893154xxx/StockTake/build/intermediates/res/merged/debug/drawable-mdpi/icon.png: error: Duplicate file.
Unknown source file : /tmp/build5662507870470893154xxx/StockTake/build/intermediates/res/merged/debug/drawable-mdpi-v4/icon.png: Original is here. The version qualifier may be implied.
Full build error is here
Any suggestion please.

Do you have a file named icon.png in one of your native directories or cn1libs?
This could collide with the icon we set into place.

Related

Legato-AF platform [ Can’t find dependent .api file: ‘le_mdc.api’ ]

In Legato-af (legato) environment:
*Linux Ubuntu
*Sierra Wireless WP76xx and WP77xx target
*Legato shell (lsh:wp76stable)
I'm getting the following response:
(lsh:wp76stable) error: Can't find dependent .api file: 'le_mdc.api'
The same error is in wp77stable profile.
The error "Can't find dependent .api file: 'le_mdc.api'" typically occurs when the Legato build system is unable to find a required API file. This can be caused by a number of issues, such as:
The API file is not present in the expected location.
Make sure that the API file is located in the correct directory and is spelled correctly.
The API file is not included in the build.
Make sure that the API file is included in the build by adding it to the appropriate component.cdef or app.cdef file.
There is a problem with the build system configuration.
Make sure that the build system is properly configured and that all required dependencies are specified.
API file
$LEGATO_ROOT/interfaces/le_data.api
is referencing
$LEGATO_ROOT/interfaces/modemServices/le_mdc.api
what is the source of the problem.
What worked for me was a simple copy of le_mdc.api
into the same folder with le_data.api

SourceLink: PDB File Name Casing Does Not Match Repository, Breaking SourceLink

Is there any way of configuring the linker in Visual Studio so that file names (and paths) embedded in the .pdb file maintain their casing?
We have a Visual Studio C++/Cli DLL that we'd like to package with NuGet. We want to use SourceLink so that our developers can step into the code, which is hosted on a (private) GitHub repository.
However, when trying to step into the source, Visual Studio (2019 16.2.2) reports an error:
Source Link Error
git-credential-manager.exe: Could not obtain credentials. Process failed with exit code -1.
ERROR: The request failed with code 404 : "Not Found". Treating 404 as authentication failure. Some services return 404 instead of 401 for authentication failures.
Source Link URL: https://raw.githubusercontent.com/OurCompany/OurRepository/aca51f6e381401234e95b63949d150be04a0ea4a/ourproject/oursubfolder/thefile.cpp
Note that on the file-system and repository the file path uses camel-casing: Ourproject/OurSubFolder/TheFile.cpp.
When I replicate the request in Postman using Basic authorisation, it does indeed fail with 404. However, the problem seems to be that the URL constructed by Visual Studio uses lower-case characters for the filename and location; correcting the case makes the request work in Postman. GitHub URLs are of course case-sensitive and that's not configurable.
Opening the .pdb file in Notepad++ shows the filenames are indeed lower-case.
For what it's worth, changing ignorecase = false in the git .config file makes no difference.
I had the exact same issue. It turns out it's a known bug, and was fixed in VS2019. Unfortunately you need to upgrade to the latest tool chain (v142).

Cannot compile resource for application manifest in C++ Builder 2006

I am trying to add the application manifest to a program built with C++Builder 2006, by following this article.
(The manifest is to obtain admin rights for my program, which contains "setup" in his name and so it triggers the “This program may not have installed correctly” warning).
I have the MyApp_Setup.exe.manifest in the project folder, along with the MyApp_Setup1.rc file, which is present in the project.
When i try to build, i get:
[RC Fatal Error] MyApp_Setup1.rc(1): File creation failed
What i'm doing wrong, or what should I do?
question edited 'cause i messed up the filenames and the output error didn't matched
Found the problem.
In the project options I always set an "_obj" output folder, but the resource compiler WANTS an existing "debug_build" folder to write the .res file.
It don't create the directory, hence the error in the file creation.
If i remove the "Obj" option, or once you have the "Debug_Build" folder present, everything compiles.

Team City - File not found error - compilation error

My team city build is failing with error
" [Csc] CSC error CS2001: Source file
'Services\Entities\ModelNames.cs' could not be found
Thing is this .cs file is deleted from source contrl (TFS) and local machines when checked in. There is no piece of code using this class anywhere in the project. But I still keep getting this error. What can I try?
Make sure your TeamCity checkout or script checkout is correct. It seems like your building using old project file. Maybe the sub directories are checked out and not the root directory as well ?

VC2008 compiler errors opening sbr files (C2418 C1903 C2471)

EDIT: See my answer below for the hotfix.
ORIGINAL QUESTION:
In setting up for our boat-programming adventure I have to set up source control and fix project files for a team to use them. (the project was previously only being worked on by one person who took shortcuts with setting up the project includes, etc)
I am fixing those SLN and Proj files. When trying to do a build on an external USB drive (I have not tried it on the primary hard drive) I am getting odd errors (lots of them for various files):
fatal error C1083: Cannot open
compiler generated file:
'.\Debug\.sbr': Permission
denied
These files are referenced in the vcproj file with relative paths in double quotes:
RelativePath="..\..\Source\.cpp"
I get the same errors form within a sln file in the IDE or if I call msbuild with the sln file.
The files are kind of "shared" for a few sln files (projects).
The person who originally created the SLN files is not known for being a wizard at configuring MSDev or making things work for teams.
Is this an issue with the way the source files are referenced? Any suggestions on how to fix these?
This URL does not seem to have helpful information:
Fatal Error C1083 on MSDN
Note - there were/are still hardcoded paths in the proj file, but i don;t see them for these files. They were mostly for the include and lib dirs. I think I removed them all.
I also get these errors:
..\..\Source\.cpp : error C2471:
cannot update program database '\debug\vc90.pdb'
..\..\Source\.cpp(336) : fatal
error C1903: unable to recover from
previous error(s); stopping
compilation
..\..\Source\.cpp(336) : error
C2418: cannot delete browser file:
.\Debug\.sbr
Title: You may receive a "PRJ0008" or "C2471" or "C1083" or "D8022" or "LNK1103" or similar error message when you try to build a solution in Visual C++
Symptoms:
D8022 : Cannot open 'RSP00000215921192.rsp'
PRJ0008 : Could not delete file 'vc90.idb'.
C1083 : Cannot open program database file 'vc90.pdb'
C2471 : Cannot update program database 'vc90.pdb'
LNK1103 : debugging information corrupt.
Cause:
This problem occurs when all of the following conditions are true:
You have a solution with more than one project in it.
Two or more of the projects are not dependent on each other.
You have parallel builds enabled. (Tools -> Options: Projects and Solutions, Build and Run: "maximum number of parallel project builds" is set to a value greater than 1)
You are building on a system with multiple CPUs (cores).
Two or more of the non-dependent projects are configured to use the same Intermediate and/or Output directory.
A specific race condition in mspdbsrv.exe remains uncorrected.
Resolution:
To resolve the problem do one or more of the following:
Reconfigure the non-dependent projects to specify an Intermediate and Output directory that is different from one another, e.g. Output Directory = "$(SolutionDir)$(ProjectName)\$(ConfigurationName)", Intermediate Directory = "$(OutDir)".
Adjust your solution's project dependencies (Project -> Project Dependencies...) so that each is dependent on another.
Disable parallel builds.
Add the "/onecpu" boot option to your boot.ini file.
Change you BIOS settings to enable/use only one CPU.
File a problem report with Microsoft Technical Support and keep bugging the crap out of them until they eventually fix mspdbsrv.
Status:
The problem is a combination of both a user project configuration error as well as a race condition in Microsoft's "mspdbsrv.exe" utility that does not properly handle more than one thread calling it at the same time for the same file resulting in the file's HANDLE being left open.
Additionally Visual Studio itself and/or its build system (VCBUILD and/or MSBUILD) (or all three!) should be made smart enough to detect and alert the user of such user errors so that corrective action can be taken.
This problem has been around for a LOOOOOONG time.
Applies to:
Microsoft Visual C++ 2005
Microsoft Visual C++ 2008
Others?
Respectfully submitted:
"Fish" (David B. Trout)
fish#infidels.org
p.s:
You're welcome. :)
Hmmm.
Perhaps:
http://social.msdn.microsoft.com/Forums/en-US/vclanguage/thread/0ceac3c6-62f6-4fdf-82e1-d41e1b4fcd20/
there is a hotfix from MS
http://code.msdn.microsoft.com/KB946040
http://support.microsoft.com/kb/946040
That might be my problem. I think it might only be on one machine I have.
EDIT:
I downloaded and ran the hotfix installer. It seems to have fixed it.
I get this same error when I physically remove a file from disk, but leave it in VS. In VS2005 it would give a much better : fatal error file not found. I think this is a bug in VS2008. The hotfix mentioned above didn't help me.
In my case it was my virus package (Trend Micro) causing all the problems. I added my Dev folders to the Ignore/White lists to solve the problem
delete your debug folder and build your project agian.
Occastionally my Visual Studio will suddenly decide something like this. I have found it maybe help to toggle to release, do a full rebuild, then toggle back to debug.